Hi all, Marko, Gordan, Hartmut, Cyrill, Just to say: Thanks to all of you for the valuable insights and feedback. Appreciated! Having read everyting we understand there is nothing to worry about, and we will need to look into cgroups. Will do. We still feel that with "vm.swappiness=1", this kind of swapping would be nicer NOT to occur. Thanks! MJ On 9/23/24 15:26, Marko Mäkelä wrote:
On Mon, Sep 23, 2024 at 2:44 PM cyusedfzfb via discuss <discuss@lists.mariadb.org> wrote:
Hi all!
New here, signed up just new, to discuss an interesting mariadb behaviour we are seeing, related to mariadb unexpectedly using swap space.
Look at this example:
RHEL 8.10, running mariadb-server-utils.x86_64 3:10.5.22-1.module+el8.8.0+20134+a92c7654: Side note: MariaDB Server 10.5.22 was released more than a year ago, in August 2023. Currently, the latest release in that series (10.5.26) is about a year newer.
Again: enough RAM available, and swap is used 3/4, mostly by MariaDB. If you are using the InnoDB storage engine, the most interesting parameter would be innodb_buffer_pool_size. There are also some other buffer size parameters that may be relevant here. Unfortunately, https://jira.mariadb.org/browse/MDEV-19895 has not been implemented yet. What is sane for one thinkable configuration would be completely insane in another.
With best regards,
Marko