[MCOL-287] CPImport performance slowdown by 27% or more from a1.0.1 to 1.0.2 Created: 2016-09-09  Updated: 2016-09-30  Resolved: 2016-09-30

Status: Closed
Project: MariaDB ColumnStore
Component/s: cpimport
Affects Version/s: None
Fix Version/s: 1.0.4

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Andrew Hutchings (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MCOL-280 Beta issues Closed
Sprint: 2016-19

 Description   

Build tested: a1.0.2-1

I did cpimport loading test and compared the results from a1.0.1. a1.0.2 is about 27% slower. This new test was done on an even more powerful AWS instance.

I don't know what caused the slowness yet and we need to investigate.

a1.0.1 was tested on instance type 4m.2xlarge
a1.0.2 was tested on instance type 4m.4xlarge

DBT3 Database a1.0.1LoadTime(s) a1.0.2LoadTime(s)
1gb 27.70 35.23
10gb 219.02 280.24
100gb 2074.79 2674.16



 Comments   
Comment by Dipti Joshi (Inactive) [ 2016-09-09 ]

dleeyhWhat mode of cpimport was used for this test and on how many nodes cluster?

Comment by Daniel Lee (Inactive) [ 2016-09-12 ]

Mode 1

Both 1PM and 1UM2PM showed similar performance.

Comment by Dipti Joshi (Inactive) [ 2016-09-12 ]

dleeyh Can we also please run mode 3 test where UM and PM are on different node ?

Comment by Andrew Hutchings (Inactive) [ 2016-09-20 ]

This is extremely likely to be the same problem as MCOL-303

Comment by Andrew Hutchings (Inactive) [ 2016-09-30 ]

The performance fix in 1.0.4 has resolved this. My own tests show a 20% performance improvement in cpimport with DBT3 1GB

Generated at Thu Feb 08 02:19:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.