On Tue, 10 Feb 2009 13:21:35 -0600, Marcy Cortes <[email protected]> wrote:
> >We've seen this messages on a new system that we build that didn't have >enough page space (yet). >You probably need some more paging volumes - add up the sum of all the >virtual machines and multiple by 2 and add *at least* that much space, >more if you are using vdisk for swap. Try to keep the % full to less >than 40. (that rule of thumb may vary depending on who you ask). > >Issue Q SRM and let us know what you have for those settings. > >Marcy I believe the current "rule of thumb" recommendation is to add up all of the sizes of the virtual machines which will be logged on at once, then add i n all the sizes of all of the vdisks which will be defined by logged on use rs, double that, and paging DASD space should be at least that large. The po int is not only to ensure there's enough paging space to hold the entire workload, but to also leave enough "breathing room" in terms of contiguou s available sets of paging slots (think entire tracks or more) to allow the block paging algorithms to work effeciently. - Bill Holder, z/VM Development, IBM Endicott
