Subj : Re: Hub 3 Update
To   : Zip
From : deon
Date : Sat Apr 13 2024 09:07 am

  Re: Re: Hub 3 Update
  By: Zip to deon on Fri Apr 12 2024 09:50 pm

Howdy,

 > I think some of the default settings for memory/virtual memory in Linux
 > leaves a lot to be desired, having vm.overcommit_memory = 0 (heuristic mode
 > which tends to fail when an application wants lots of memory fast),
 > vm.overcommit_ratio = 50 (only allow applications to use 50% of physical
 > RAM) and vm.swappiness = 60 (rather high tendency to use swap).

So in my case, there is another element, which is the memory limit assigned to the docker container. I do that so 1 container doesnt starve the resources for others.

docker "stats" shows the DB hovering around 200MB of ram, with the ability to use 512MB - so I thought that was well enough. But underload the oom-killer would kill it.

The host has plenty of swap available (only using 5% and using <50% of system RAM (with cache buffers), so not sure why it was selected to kill. I guess it's quite possible a large (infrequent) query consumed all memory. Anyway giving it 1GB hasnt seen it be killed in 12 hrs...

 > Hope this helps!

Thanks...


....лоеп
--- SBBSecho 3.20-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.