Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!purdue!decwrl!ucbvax!DRCVAX.ARPA!graham From: graham@DRCVAX.ARPA Newsgroups: comp.os.vms Subject: RE: MPW_HILIMIT Message-ID: <8807270436.AA28100@ucbvax.berkeley.edu> Date: 20 Jul 88 12:21:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Organization: The Internet Lines: 33 On the subject of the MPL discussion, Mike Pung correctly writes: >One comment concerning Frank's response is to note that the ALL-IN-1 product >DOES use global sections and thus each time an ALL-IN-1 user's process >terminates the Modified Page List (MPL) is flushed (i.e. ALL pages are >written, not just down to MPW_LOLIMIT). So if your are running ALL-IN-1 and >you have a large MPL, then you may see pauses in the system as the >Modified Page Writer is busy clearing the MPL. In this case, it would be >better to set a moderate to small MPL and set up large user working sets. I am running, among other things, a Microvax II for nothing but All-in-1. This machine has 16 mb of memory, so resources are not a problem. I have played "Tune-up Masters" with thie machine for two years. Mike is right, a 500 page MPL is the largest it should be, and 300 does not do badly either. We use 2500 page working sets and find that we get good response. I did some extensive revisions of other sysgen parameters, though. The idea of freelim being only 100 or so blocks by default rubbed me the wrong way, so I raised freelim to 1000. I then had to adjust freegoal, borrowlim, weinc and wedec, also. Finally, we have a system where about 16-18 allin1 users can coexist pretty well. Another important thing with Allin1, be sure they aren't using the qualifier that creates a default subprocess unless they ABSOLUTELY need it. Those subprocesses eat up memory and are a big waste. Just my $0.02 worth, Dan Graham graham@drcvax.arpa -------------------------------------------------------------- "You're kidding, THAT is an opinion? THAT is drivel!!" ------