Re: Chasing OOM Issues - good sysctl metrics to use?

From: Jeffrey Bouquet <jbtakk_at_iherebuywisely.com>
Date: Sat, 23 Apr 2022 16:35:49 UTC

On Fri, 22 Apr 2022 16:46:20 -0700, Pete Wright <pete@nomadlogic.org> wrote:

> 
> 
> On 4/22/22 13:39, tech-lists wrote:
> > Hi,
> >
> > On Thu, Apr 21, 2022 at 07:16:42PM -0700, Pete Wright wrote:
> >> hello -
> >>
> >> on my workstation running CURRENT (amd64/32g of ram) i've been running
> >> into a scenario where after 4 or 5 days of daily use I get an OOM event
> >> and both chromium and firefox are killed.  then in the next day or so
> >> the system will become very unresponsive in the morning when i unlock my
> >> screensaver in the morning forcing a manual power cycle.
> >
> > I have the following set in /etc/sysctl.conf on a stable/13 
> > workstation. Am using zfs with 32GB RAM.
> >
> > vm.pageout_oom_seq=120
> > vm.pfault_oom_attempts=-1
> > vm.pageout_update_period=0
> >
> > Since setting these here, OOM is a rarity. I don't profess to exactly 
> > know
> > what they do in detail though. But my experience since these were set
> > is hardly any OOM and big users of memory like firefox don't crash.
> 
> nice, i will give those a test next time i crash which will be by next 
> thurs if the pattern continues.
> 
> looking at the sysctl descriptions:
> vm.pageout_oom_seq: back-to-back calls to oom detector to start OOM
> vm.pfault_oom_attempts: Number of page allocation attempts in page fault 
> handler before it triggers OOM handling
> vm.pageout_update_period: Maximum active LRU update period
> 
> i could certainly see how those could be helpful.  in an ideal world i'd 
> find the root cause of the system lock-ups, but it would be nice to just 
> move on from this :)
> 
> cheers,
> -p
> 
> -- 
> Pete Wright
> pete@nomadlogic.org
> @nomadlogicLA


I don't know if it would help this discussion, but I installed security/picocrypt
and memory usage started going thru the roof*. Maybe that port could be used to
test any fix found in this thread, iow if that port runs better without /with some
sysctl... if could be used for the issues discussed here so far.  
  * and I had to desintall.  FWIW I had set the three vm listed above  a short
while prior.