On Wed, Jul 27, 2022 at 4:26 PM jocelyn fournier <jocelyn.fournier@gmail.com> wrote:
It’s not that tiny, this article is a bit old, but still valid:
https://www.percona.com/blog/2008/11/21/how-to-calculate-a-good-innodb-log-f...
If you don’t need a big redo log, reduce its side to avoid slow crash recovery
Starting with MariaDB Server 10.5, recovery should run faster than in earlier versions, thanks to the easier-to-parse log format (MDEV-12353) and some memory management optimizations such as MDEV-21351. Furthermore, MariaDB 10.5 should not run out of memory on recovery even when starting up with innodb_buffer_pool_size that is smaller than innodb_redo_log_size. In earlier versions, the calculations to avoid running out of memory are inaccurate. A too small redo log may cause backup to fail, depending on the write rate of the server. A server-assisted backup (some ideas are in MDEV-14992) would solve that. Marko