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
That looks to me like a write to the header page each time a transaction is started. You have a 32KiB page size by the looks of it. This is entirely expected and normal if you (or a driver in auto-commit mode) starts a new transaction for each select, and executes those selects near continuously.
Activity
mrotteveel commentedon Dec 22, 2025
That looks to me like a write to the header page each time a transaction is started. You have a 32KiB page size by the looks of it. This is entirely expected and normal if you (or a driver in auto-commit mode) starts a new transaction for each select, and executes those selects near continuously.
hvlad commentedon Dec 22, 2025
And why do you think it is not correct, or problem, or ... what ?
Note, you use biggest possible database page size, also, you disabled filesystem caching - no wonder it creates some load on IO.
PS usage of read-only transactions when possible will lower header page writes.
mrotteveel commentedon Dec 22, 2025
I thought that was no longer the case with ReadConsistency = 1
hvlad commentedon Dec 22, 2025
I speak about #5706 (CORE-5434)
mrotteveel commentedon Dec 22, 2025
@hvlad Do you think this should be moved to discussions?
hvlad commentedon Dec 22, 2025
Yes, please. So far I see no bug or real issue here.