M.P.A. -- Memory Performance Analyzer ---------------------------------------- (C) Copyright 1988 by Rand P. Hall and M.P.Gerlek All Rights Reserved 21-Mar-88 : v1.0 (initial test) Designed by: Rand P. Hall Coded by: M.P.Gerlek 910 Riverside Drive 2 Robinson Drive Methuen, MA 01844 USA Bedford, MA 01730 USA "All lovers swear more performance than they are able, And yet reserve an ability that they never perform." - William Shakespeare, "Troilus and Cressida" (III,ii,89) MPA - Directions --- ---------- How MPA works. MPA is designed to assist you in maximizing the performance of your memory subsystem. MPA performs both the collection and analyzation parts of the tuning process. MPA has an internally defined set of rules. It collects the data necessary to analyze the rules and then after analyzing them it explains the problems it found and suggests ways to eliminate the problem. MPA has two different sets of rules. The first set analyzes the composition of the portion of memory occupied by the operating system. If too large this portion of memory will take away memory that could be used by user processes. If too small the operating system could start paging itself out of memory degrading the performance of all processes. MPA attempts to optimize the size of system-occupied memory with its type 1 (aka "SVASS", system virtual address space sizer) rules. We have found that Autogen typically makes non- paged pool much too large. Rules of type 1 correct this. We've witnessedd savings of .25 - .5MB on the systems we've tested this on. MPA's type 2 ("MPAP") rules attempt to optimize the way the operating system manages its memory. VMS' memory management system can be tailored to react in certain ways to certain situations, hence it can be altered to react favorably to your particular work load. MPA analyzes your work load and the way memory management currently functions and suggests ways to tailor memory management to your system's environment for maximum output.