Comments on: MySQL 8.0 Dynamic Redo Log Sizing

By: Vinicius Grippa

Vinicius Grippa — Thu, 01 Dec 2022 21:25:30 +0000

Hi Draw,
No, there is no need because, with the new redo log sizing, MySQL automatically manages the underlying files. For example, if you calculated the ideal redo size and found it is 10GB.
You need to run the following:

mysql> SET GLOBAL innodb_redo_log_capacity = 10*1024*1024*1024;

1	mysql> SET GLOBAL innodb_redo_log_capacity = 1010241024*1024;

Let me know if it helps!

By: Vinicius Grippa

Vinicius Grippa — Thu, 01 Dec 2022 21:23:35 +0000

In reply to Draw. Hi Draw, No, there is no need because, with the new redo log sizing, MySQL automatically manages the underlying files. For example, if you calculated the ideal redo size and found it is 10GB. You need to run the following: mysql> SET GLOBAL innodb_redo_log_capacity = 10*1024*1024*1024; Let me know if it helps!

By: Draw

Draw — Tue, 29 Nov 2022 18:37:20 +0000

Hi
Should we divide “equivalent to 15GB” on the number of log file members like in the blog post from 2008?