Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 May 2022 20:42:50 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: Chasing OOM Issues - good sysctl metrics to use?
Message-ID:  <499358a4-beec-67d1-460c-3fe61781fb0c@nomadlogic.org>
In-Reply-To: <CE2AA4C9-293A-4C87-A619-DABAC1141494@yahoo.com>
References:  <8C14A90D-3429-437C-A815-E811B7BFBF05.ref@yahoo.com> <8C14A90D-3429-437C-A815-E811B7BFBF05@yahoo.com> <b6017cc8-3734-da81-8c73-5715f2e3ff94@nomadlogic.org> <CE2AA4C9-293A-4C87-A619-DABAC1141494@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On 5/29/22 11:16, Mark Millard wrote:
>
> FYI, the combination:
>
> vm.pageout_oom_seq=120 # in /boot/loader.conf
> vm.swap_enabled=0      # in /etc/sysctl.conf
> vm.swap_idle_enabled=0 # in /etc/sysctl.conf
>
> still has not caused me any additional problems
> and helps avoid loss of access by avoiding the
> relevant interaction-processes from having their
> kernel stacks swapped out. (Not that the effect
> of vm.swap_enabled=0 is limited to
> interaction-processes.)
>
> So, the combination is now part of the
> configuration of each FreeBSD that I use.

awesome thanks Mark!  i appreciate your feedback and input, i've 
certainly learned quite a bit as well which is awesome.

i'm going to revert the diff as well when i kick off my weekly rebuild now.

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499358a4-beec-67d1-460c-3fe61781fb0c>