Hello,
I have a long-standing problem on my nas that I can't solve, I don't understand the behavior of the kernel in relation to RAM usage.
I have a DS220+ with 18GB of RAM that works fine overall but has a nasty tendency to swap excessively with a huge amount of cached memory available, which generates a lot of I/O disk access and slows down the whole system :
I know that kernels are configured to use as much cache memory as possible to speed up the system, but in my case it's excessive, I have the impression that the system refuses to free up cache memory, even if it means swapping highly active data like MariaDB databases of the "Servarr app suite" :
I use Dockers containers, which I suspect to have memory leaks (transmission in particular), I have limited the use of RAM in docker compose to 512Mb per container. Despite this, cache usage is always a priority and always generates swap.
I tried different kernel settings to limit swap usage, which doesn't change anything:
If someone has already encountered this problem or has a solution to propose, I am highly interested!
Thanks in advance
I have a long-standing problem on my nas that I can't solve, I don't understand the behavior of the kernel in relation to RAM usage.
I have a DS220+ with 18GB of RAM that works fine overall but has a nasty tendency to swap excessively with a huge amount of cached memory available, which generates a lot of I/O disk access and slows down the whole system :
I know that kernels are configured to use as much cache memory as possible to speed up the system, but in my case it's excessive, I have the impression that the system refuses to free up cache memory, even if it means swapping highly active data like MariaDB databases of the "Servarr app suite" :
I use Dockers containers, which I suspect to have memory leaks (transmission in particular), I have limited the use of RAM in docker compose to 512Mb per container. Despite this, cache usage is always a priority and always generates swap.
I tried different kernel settings to limit swap usage, which doesn't change anything:
If someone has already encountered this problem or has a solution to propose, I am highly interested!
Thanks in advance