Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Innodb buffer can fill up on things like during a mariadb-dump.
The logically successor to MDEV-25340 to keep only the memory required for innodb actually mapped is as part of the LRU to purge off old pages if they really haven't been used in a while. These will be still allocated to mariadbd, however in a virtual non-paged in sense.
This can be done on linux with madvise(MADV_FREE) (Linux and FreeBSD). Windows has VirtualFree MEM_DECOMMIT/MEM_RESET.
These a proactive releases, and them mechanisms implemented can be reused to serve reactive mechanism like MDEV-24670.
Attachments
Issue Links
- causes
-
MDEV-31953 madvise(frame, srv_page_size, MADV_FREE) is causing a performance regression
- Closed
- relates to
-
MDEV-29429 "free" innodb pages from dropped table/index/(deleted?)/table rebuild
- Open
-
MDEV-29431 SQL interface and Storage Engine interface for reclaiming memory
- Open
-
MDEV-29432 innodb huge pages reclaim
- Open
-
MDEV-29445 reorganise innodb buffer pool (and remove buffer pool chunks)
- Stalled
-
MDEV-24670 avoid OOM by linux kernel co-operative memory management
- Closed
-
MDEV-25340 Server startup with large innodb_buffer_pool_size takes a long time
- Open
-
MDEV-25342 autosize innodb_buffer_pool_chunk_size
- Closed