Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA.UUCP Newsgroups: mod.computers.vax Subject: Re: Tuning Message-ID: <8703260301.AA07802@ucbvax.Berkeley.EDU> Date: Wed, 25-Mar-87 22:35:23 EST Article-I.D.: ucbvax.8703260301.AA07802 Posted: Wed Mar 25 22:35:23 1987 Date-Received: Fri, 27-Mar-87 06:07:10 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Distribution: world Organization: The ARPA Internet Lines: 17 Approved: info-vax@sri-kl.arpa [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 -------