![](https://secure.gravatar.com/avatar/3bce7f356a04335a99fe8b1a74a04e02.jpg?s=120&d=mm&r=g)
Hi Kazuhiko, all, On Sat, Dec 14, 2024 at 12:58 AM <kazuhiko@nexedi.com> wrote:
Sorry, 10.6.13 seems 'not always' good.
I tried 10.6.13 with 4GB log file and 256MB log file cases (buffer pool size is 16GB on both tests).
No history length increase issue on 10.6.13 with 4GB log file. BUT quite bad behaviour on 10.6.13 with 256MB log file, i.e. some history length caused by cleanup process still remained at the beginning, and increased history length remained even after everything finished. Also 1-2 seconds stall happened several times. (see the attached graphs)
On 10.5.20, I had no such issue on both 4GB log file and 256MB log file, and its behaviour was quite 10.4.34.
Can you (or anyone) post a test script as well as some details of the test environment that is reproducing this regression? I would need to reproduce this regression in order to analyze and fix it. Best regards, Marko -- Marko Mäkelä, Lead Developer InnoDB MariaDB plc