🚀 go-pugleaf

[The author described a 750 set up with a very large WSEXTENT and a moderate
size WSQUOTA, used mainly to run a single very large process.  Every once in
a while, a process that's been happily running using all of its WSEXTENT is
suddenly knocked down to its WSQUOTA.  The question is, why?]

Quick guess:  If I remember right, the Swapper will trim a process back to
WSQUOTA before swapping it out.  This would give the symptoms you describe.
As to WHY the Swapper would decide it was time for the process to be swapped,
I can't say.  Running one process above BALSETCNT would do it, and the extra
process could be something like a network server started up to receive some
mail, for example.

You don't mention what you have BALSETCNT set to, but given your other numbers
and your intended usage of the machine I'd guess you have it set fairly small.

							-- Jerry
-------