Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.11.12, 11.4.6
-
Ubuntu 24.04
Description
After upgrading from MariaDB 11.4.5 to 11.4.6, we observed that the InnoDB buffer pool now reserves all configured memory at startup htop show both RES and VIRT at max pool memory , even though actual usage is minimal. This behavior was not present in MariaDB 11.4.5. There are also new InnoDB variables like innodb_buffer_pool_size_auto_min that are not present in documentation. But assuming from its name it should help mariadb dynamically reserve memory between its value and pool memory depending on load. However changing this value have zero effect. Additional the update changed the chuck size to 0. Why?
Attachments
Issue Links
- is caused by
-
MDEV-29445 reorganise innodb buffer pool (and remove buffer pool chunks)
-
- Closed
-
- relates to
-
MDEV-36759 huge performance drop after update
-
- Closed
-