Jim Bohnsack
2006-02-06 20:56:14 UTC
Duane--My experience in running multiple guest MVS systems is to give them
a virtual size such that their working sets will generally fit in storage
causing the MVS system itself to manage and do it's own paging. One thing
that you absolutely do not want to happen to a production guest is to have
it not be dispatchable because of a page fault. MVS is good at
paging. Let it page. You'll have to experiment to find the optimum
size. Use the Perf. Toolkit or ESAMON or something like that.
Jim
At 03:49 PM 2/6/2006, you wrote:
>I have a VM system that is going to host 2-3 ZOS guest systems running at
>the same time.
>
>The z/VM system is running the default service machines, including TCPIP
>and FTPSERVE.
>
>The VM system itself has a total of 3152m of storage.
>
>How does one determine how much storage can be given to one or more zOS
>guests?
>
>
>Duane
>Ohio State U.
Jim Bohnsack
Cornell Univ.
(607) 255-1760
a virtual size such that their working sets will generally fit in storage
causing the MVS system itself to manage and do it's own paging. One thing
that you absolutely do not want to happen to a production guest is to have
it not be dispatchable because of a page fault. MVS is good at
paging. Let it page. You'll have to experiment to find the optimum
size. Use the Perf. Toolkit or ESAMON or something like that.
Jim
At 03:49 PM 2/6/2006, you wrote:
>I have a VM system that is going to host 2-3 ZOS guest systems running at
>the same time.
>
>The z/VM system is running the default service machines, including TCPIP
>and FTPSERVE.
>
>The VM system itself has a total of 3152m of storage.
>
>How does one determine how much storage can be given to one or more zOS
>guests?
>
>
>Duane
>Ohio State U.
Jim Bohnsack
Cornell Univ.
(607) 255-1760