[MDEV-17426] measure impact of innodb_log_optimize_ddl Created: 2018-10-11  Updated: 2018-10-11

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: None

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


 Description   

Measure the actual performance difference between innodb_log_optimize_ddl=OFF and the default ON, in 10.2, on ALTER TABLE…ADD INDEX…, ALGORITHM=INPLACE or ALTER TABLE…FORCE, ALGORITHM=INPLACE, both for small and big tables, both for small and big buffer pool (with lots of other tables populating the buffer pool).

If the reduced redo logging does not seem to offer much benefit (it does require an extra buffer pool scan & page flush before re-enabling logging), then maybe we could set this option OFF by default


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