You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Feature Request
Please consider automatically enabling --innodb-optimize-keys for innodb tables with more than 1 index and more than 1 million records.
Current behaviour
I attempted to import a database which includes a table with 0.3 billion records and 10 indexes.
It very quickly slowed to an absolute crawl - after 24 hours I calculated the current velocity and it would've taken a minimum of a week to complete, but in reality much more as it was becoming slower and slower.
I used --innodb-optimize-keys and disabled the "optimisation" in #987 (set UNIQUE_CHECKS back to 0), and the import completed in a few hours.
Expected behavior
Myloader should be able to identify large/complex tables and apply optimisations accordingly
Environment
Linux/AMD64/Gentoo
10.6.17-MariaDB-log
The text was updated successfully, but these errors were encountered:
davidducos
changed the title
--innodb-optimize-keys
Add --auto to automatically configure mydumper and myloader
May 10, 2024
davidducos
changed the title
Add --auto to automatically configure mydumper and myloader
Add --innodb-optimize-keys=SKIP to ignore the new enabled default --innodb-optimize-keys option
May 10, 2024
Describe the Feature Request
Please consider automatically enabling --innodb-optimize-keys for innodb tables with more than 1 index and more than 1 million records.
Current behaviour
I attempted to import a database which includes a table with 0.3 billion records and 10 indexes.
It very quickly slowed to an absolute crawl - after 24 hours I calculated the current velocity and it would've taken a minimum of a week to complete, but in reality much more as it was becoming slower and slower.
I used --innodb-optimize-keys and disabled the "optimisation" in #987 (set UNIQUE_CHECKS back to 0), and the import completed in a few hours.
Expected behavior
Myloader should be able to identify large/complex tables and apply optimisations accordingly
Environment
Linux/AMD64/Gentoo
10.6.17-MariaDB-log
The text was updated successfully, but these errors were encountered: