[MDEV-17353] pinpoint perf regressions in early 10.3 to commits Created: 2018-10-02  Updated: 2020-02-18

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Axel Schwenke Assignee: Axel Schwenke
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16168 Performance regression on sysbench wr... Closed

 Description   

The regression suite shows some performance regressions in early 10.3 releases. Those should be tracked to commits.

 Comments   
Comment by Axel Schwenke [ 2018-10-02 ]

example: t_oltp_innodb_single, 10.3.4 to 10.3.5

Comment by Marko Mäkelä [ 2018-10-04 ]

In MDEV-16168 there was some attempt to narrow down these regressions.

Comment by Axel Schwenke [ 2020-02-18 ]

The new 90:10 OLTP test for MENT-635 shows two major regressions during the early 10.3 development:

mariadb-10.2.5          3914.0  20646   36738   56478   63304   65822   63426
 
mariadb-10.3.0          3879.7  20596   36374   54762   60568   62766   60943 <--- Regression!
 
                                                -----   -----   -----   -----
 
mariadb-10.3.1          3868.2  20847   36731   54344   60187   62145   59690
 
mariadb-10.3.2          3913.8  21135   37337   56532   63417   65588   63088
 
mariadb-10.3.3          3924.2  21741   38862   53970   59869   61966   59546 <--- Regression!
 
                                                -----   -----   -----   -----

One in 10.3.0 and the other in 10.3.3.

Generated at Thu Feb 08 08:35:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.