[MCOL-4396] MariaDB X5 10.5.6 takes a very long time to load data compared to ColumnStore 1.2.5 Created: 2020-11-18 Updated: 2023-07-05 |
|
| Status: | Open |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
From Customer: New cluster created What is your opinion on changing to this alternate table engine configuration? Do you think using the CrossEngine Join feature on 8 to 18 tables (or more) in a single query would be problematic? I take it all of those CrossEngine joins would be processed on pm1. Is there any hope that X5 using the columnstore engine can get its load data times back down in the 2 sec range for the the sample table provided? A side effect of this new configuration would be that the convert_tz function would be working to create the view on an InnoDB table instead of a Columnstore table. |
| Comments |
| Comment by David Hill (Inactive) [ 2020-11-18 ] | ||
|
As an example, the table described below took 2 seconds to create and load 188 records on ColumnStore 1.2.5 and 23 seconds on MariaDB X5 10.5.6 Both tests used LOAD DATA LOCAL INFILE statements. That indicates our ETL process will take 11x longer to complete on MariaDB X5. This is a serious performance issue. The table definition is the same on both systems. > select count
----------
---------- The ColumnStore cluster has 1 um and 2 pm nodes. The MariaDB X5 system has 3 nodes running MaxScale in front of the pm's. |