[MDBF-528] MyDumper restoration performance regression with MariaDB 10.6 Created: 2023-01-24 Updated: 2023-01-31 Resolved: 2023-01-31 |
|
| Status: | Closed |
| Project: | MariaDB Foundation Development |
| Component/s: | None |
| Affects Version/s: | N/A |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Hutchings | Assignee: | Andrew Hutchings |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| Description |
|
MyDumper has a performance regression when using the myloader restoration tool in MariaDB 10.6. This is because setting UNIQUE_CHECKS=0 in MariaDB 10.6 puts InnoDB into a special mode to increase performance for single threaded bulk inserts. Unfortunately this implements a table level lock which actually significantly reduces the performance of myloader. |
| Comments |
| Comment by Andrew Hutchings [ 2023-01-24 ] | ||
|
Pull request open here: https://github.com/mydumper/mydumper/pull/988 This fixes the MariaDB detection, lays the groundwork for detecting things like sequences and system version tables, as well as removes the "UNIQUE_CHECKS=0" call for MariaDB. In addition a workaround is possible, creating a MyDumper configuration file with:
| ||
| Comment by Andrew Hutchings [ 2023-01-24 ] | ||
|
In review with MyDumper team | ||
| Comment by Andrew Hutchings [ 2023-01-31 ] | ||
|
This has been merged upstream. |