[MDEV-15242] Poor RBR update performance with partitioned tables Created: 2018-02-07 Updated: 2020-08-25 Resolved: 2018-06-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Partitioning, Replication, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.34, 10.1.31 |
| Fix Version/s: | 10.0.36, 10.1.35, 10.2.17, 10.3.8 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Andrei Elkin |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | innodb, partitioning, upstream | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
This is related to the following upstream bug: https://bugs.mysql.com/bug.php?id=73648 When binlog_format=ROW is set and a partitioned table is updated, the update seems to perform much slower than an equivalent update of a non-partitioned table. Some MTR tests have been contributed to demonstrate this problem. They are in the attached zip archive. The results were reported as the following:
MySQL 5.7 most likely performs better because of the introduction of native partitioning. Native partitioning was removed from MariaDB 10.2 during the 5.7 InnoDB merge. See |
| Comments |
| Comment by Andrei Elkin [ 2018-06-19 ] |
|
Sergei, hello. Find below is a patch header. [I had to struggle for few hours Cheers, Andrei From: andrei.elkin@pp.inet.fi revision-id: 37b432c1d59e66b742f97a280cae7784d85e62ec (mariadb-10.0.35-41-g37b432c1d59)
Observed and described Fixed with applying an upstream patch. References: |
| Comment by Andrei Elkin [ 2018-06-26 ] |
|
The patch is pushed as 28e1f1453f1. |
| Comment by Chris Calender (Inactive) [ 2018-06-28 ] |
|
Elkin or Anyone else who might know: Will this be fixed in the next 10.1, which will be 10.1.35 (tentatively scheduled for 7/27/18)? Many thanks in advance. |
| Comment by Julien Fritsch [ 2018-06-28 ] |
|
I'mm 90% sure yes ccalender |