re: port-powerpc/56818: oea: system trapped in pgdaemon under high memory pressure

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR port-powerpc/56818; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: Rin Okuyama <rokuyama.rk%gmail.com@localhost>
Cc: gnats-bugs%netbsd.org@localhost, port-powerpc-maintainer%netbsd.org@localhost,
    gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: re: port-powerpc/56818: oea: system trapped in pgdaemon under high memory pressure
Date: Sun, 08 May 2022 05:35:25 +1000

 Rin Okuyama writes:
 > On 2022/05/07 21:00, Martin Husemann wrote:
 > >   Can you "show uvmexp", continue, break again after a few seconds and=
  repeat
 > >   a few times?
 >
 > Here's 4 successive "show uvmexp" with ~10 sec between continue and brea=
 k:
 >
 > https://gist.github.com/rokuyama/d27a0fd3a442fe1a5c9ccd5eed260ac8
 >
 > and this is diff between them:
 >
 > https://gist.github.com/rokuyama/9ababdc91b553f76deec22152f31e015
 
 i see that file pages are ~60% of the system memory.
 
 what are the vm.{file,anon,exec}{min,max} values?  the default for
 file{min,max} are {10,50}, so it should be ejecting at least 10%
 of memory really easily to get under filemax.  if those pages are
 dirty why aren't they being paged out... (system boot, and pools
 are also using about 15% of memory currently..)
 
 
 .mrg.