[MCOL-425] Performance comparison between InnoDB and ColumnStore dimension tables Created: 2016-11-29 Updated: 2021-06-23 Resolved: 2021-06-23 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Trivial |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
What is the performance difference between using InnoDB and ColumnStore dimension tables? Which one should be use if there is a choice? |
| Comments |
| Comment by Daniel Lee (Inactive) [ 2017-06-08 ] |
|
Single server installation, ColumnStore 1.0.9-1 dbt3 10g All tables are in ColumnStore disk run: 10.75 sec orders in InnoDB, lineitem in ColumnStore Query: select count All tables are in ColumnStore customer in InnoDB, orders and lineitem in ColumnStore Query: select count |
| Comment by Daniel Lee (Inactive) [ 2017-06-08 ] |
|
I forgot to create primary key and index for innodb tables in the previous test. ALTER TABLE customer ADD PRIMARY KEY (c_custkey); Query: select count All tables are in ColumnStore (from previous test) customer in InnoDB, orders and lineitem in ColumnStore Also added another test with a filter Query: select count All tables are in ColumnStore customer in InnoDB, orders and lineitem in ColumnStore |
| Comment by Daniel Lee (Inactive) [ 2017-07-10 ] |
|
Not sure what else needs to be done for this ticket. I am setting it to unassigned now. |