Question Optmized values for MariaDB

[tanasis]

but the swap file will not be cleared afterwards as that would be an unnecessary operation. So it is thinkable that the swap usage you are seeing is no current swap usage, but leftovers from a previous RAM excession.

Is it a problem?
Please also check my previous post.
Thank you!

 

[Bitpalast]

Look, noone can tell you if your 22 GB inno_db_buffer_size is a good value for your server. If your RAM is excessively overused by MariaDB, then your RAM is just too small for the configuration or your configuration is inappropriate for the RAM that your server has. If your RAM is 64 GB and a 22 GB cache of MariaDB leads to swapping, it's not actually MariaDB, but other processes on the server that consume too much RAM. It cannot be that hard to look into the process list which processes are consuming the most RAM and breaking that down to the root cause.

Many sources on MariaDB in forums say that admitting up to 70% of available RAM to the InnoDB buffer is fine, but if there are other processes on your machine that require more RAM, that RAM will not be available for MariaDB. Who knows. It just needs to be carefully checked on the server what the server is using for which process(es), and then, in a further step, it needs to be determined if you can either reduce the overuse by other processes or if you need more RAM to avoid swapping.

 

[tanasis]

Look, noone can tell you if your 22 GB inno_db_buffer_size is a good value for your server. If your RAM is excessively overused by MariaDB, then your RAM is just too small for the configuration or your configuration is inappropriate for the RAM that your server has. If your RAM is 64 GB and a 22 GB cache of MariaDB leads to swapping, it's not actually MariaDB, but other processes on the server that consume too much RAM. It cannot be that hard to look into the process list which processes are consuming the most RAM and breaking that down to the root cause.

Many sources on MariaDB in forums say that admitting up to 70% of available RAM to the InnoDB buffer is fine, but if there are other processes on your machine that require more RAM, that RAM will not be available for MariaDB. Who knows. It just needs to be carefully checked on the server what the server is using for which process(es), and then, in a further step, it needs to be determined if you can either reduce the overuse by other processes or if you need more RAM to avoid swapping.

Thank you for your reply @Bitpalast

My top30 in swap:


My current htop status:

Never see memory more than 26G even I have 62G, why this ?


As you told before : "...but the swap file will not be cleared afterwards as that would be an unnecessary operation. So it is thinkable that the swap usage you are seeing is no current swap usage, but leftovers from a previous RAM excession."

So, MariaDB has 11GB in swap right now. Is it leftovers from a previous RAM excession ?

 

[n0fear]

Hi i got 2 questions on this:

1. Does Plesk Optimizer not check how much ram is free or installed? on both my servers one with 64 GB Ram and one with 128 GB ram the innodb_buffer_pool_size ist set to 128m after optimizing?! That was before updateing to the latest Version, that is as i know not suppported. As i have plenty of ram free, i guess is makes sense to set for example innodb_buffer_pool_size = 16G, not?

2. I added the plesk optimizing vallues (just rised the buffer size) to mariadb.cnf - however as i noticed today they are not there anymore and the value is set back to 250 mb. I am not sure, but i guess it came from an update, have to investigate this again. Where is the best place to add this on a plesk server to be consitent? I saw there is a db-performance.cnf added from plesk before? but i guess this i always overwritten?