Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!decvax!decwrl!ucbvax!info-vax From: MHJohnson@HI-MULTICS.ARPA (Mark Johnson) Newsgroups: mod.computers.vax Subject: Re: System Tuning Message-ID: <851205162605.536519@HI-MULTICS.ARPA> Date: Thu, 5-Dec-85 11:26:00 EST Article-I.D.: HI-MULTI.851205162605.536519 Posted: Thu Dec 5 11:26:00 1985 Date-Received: Sat, 7-Dec-85 02:15:56 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 31 Approved: info-vax@sri-kl.arpa We have a 780 with 10mbyte of memory (785 upgrade & 6mbyte more on loading dock...) and use AUTOGEN ok. We have a moderate interactive load with a few VERY large jobs that usually run in batch. Peak logins are around 25 or so. Just looking, we use about 15.8% of memory permanently allocated to VMS. Some of the key items I have put into MODPARAMS.DAT include: WSMAX=8096 VIRTUALPAGECNT=32768 SRPCOUNT=1900 IRPCOUNT=900 BALSETCNT=36 PFRATL=0 FREELIM=200 BORROWLIM=1000 MPW_LOWLIM=200 SWPOUTPGCNT=512 NPAGEDYN=450000 PAGEDYN=300000 SWAPFILE=48000 In comparison with AUTOGEN, I have really increased several parameters that cause MORE memory to be used. A key change is the small (relative to AUTOGEN) balance set count. On my system, this causes a moderate number of jobs (up to 10 or so) to be swapped & stay swapped during peak periods. The system performance really improved after the BALSETCNT change because the jobs in memory have far reduced paging rates & there is enough free memory for image activation as well. By the way, be sure you crank up the values of IRPCOUNT & SRPCOUNT & NPAGEDYN on your system. Don't let VMS grow those values on the fly unless you like real performance hits. You can use SHOW MEMORY/ALL/FULL to get an idea what your real need is & add about 20% to that value to allow for growth. There are a couple ways your system will crash if NPAGEDYN is not big enough as well. --Mark