u From:	HENRY::IN%"MACALLSTR%vax1.physics.oxford.ac.uk%cs.ucl.ac.uk%sri-kl.ARPA%relay.cs.net@rca.com" 21-MAR-1987 18:42 0 To:	INFO-VAX <INFO-VAX%sri-kl.arpa@cs.ucl.ac.uk> Subj:	VMS tuning.   K Before anyone starts hacking/tweaking their SYSGEN parameters, my advice is '   DON'T - until you know your workload. I Let AUTOGEN give you the first 'stab' at setting SYSGEN parameters. Check N   through them to ensure that they're realistic for your system. Some packagesL   ( networking, databases, etc ) may require ( and will usually recommend inO   the documentation ) some parameters to be increased - SYSGEN won't know about    that. N Run all classes of the MONITOR utility ( + DISKS class ) over a period of timeL   to discover what your 'typical' system demands are. There's a procedure inM   SYS$EXAMPLES which will do this for those new to VMS and will provide daily 1   summaries. Old hands can benefit from this too. P Look for excessively high/low counts. Meaning of 'high/low' depends on processor    type, disk configuration,etc. J MONI xxx/current or SHOW SYS are quick ways of finding processes with highJ   paging and I/O rates. Try to find out why the rates are high. You may beN   short of memory but, on the other hand, the process may simply be performing   a lot of I/O. M Also check interactive response at the terminal, turn-round times for various L   activities,etc. Do they meet with your expectations? Are your expectationsJ   realistic? (You can't expect the same turnround on a micro-VAX for a CPUM   bound task as on an 8700! More powerful processors can also handle more I/O L   processing - but, remember, if all I/O is to/from one disk device, you may)   be limited by the speed of the device.) L How you arrange the memory use SYSGEN parameters ( WSMAX,etc ) and AUTHORIZEI   settings for WSQUOTA,etc depends on your job mix. For example, consider    three types of system.J   (1) All users run interactively, at the same priority, and are generally       CPU bound.H   (2) Users run interactively at one priority, batch jobs run at a lowerG       priority. During the day there is almost no CPU time available to        batch jobs. M   (3) Users run interactively at one priority, batch jobs at a lower priority N       but there are short lulls every ten minutes or so in the interactive use-       when batch jobs can use some CPU time.  Q The settings of the SYSGEN parameters re: swapping/paging will be quite different N  for each case. The actual values will depend on how much free memory you haveM  and how much physical memory a particular program requires. This last remark N  is very important. Each program has a 'critical working set size' below whichM  it will page like mad and above which paging will occur at normal rates. You L  ought to check that high paging rates aren't due to this. You could waste aN  great deal of effort in tuning if this is the cause of high paging rates. GetO  to know your work load and monitor jobs which have high paging rates to ensure R  that working set sizes are adequate and also to check for bad program design,etc.  L Reading the VMS Tuning manual explains the major aspects of tuning. I'd alsoL  recommend reading the SYSGEN parameter explanations in the SYSGEN manual soM  that you have some understanding of the effects of adjustments and, perhaps, M  to suggest to you other ways in which you might tune your particular system.   J If you do make adjustments change only ONE thing at a time ( or one set ofI  related parameters ). If you become too deeply immersed in tuning you'll I  never be satisfied - quit when you're nearly there; don't wait until you   arrive - it'll never happen!    John