On 2/2/06, Stefan Raabe <[EMAIL PROTECTED]> wrote: We should probably take the Linux discussion to the LINUX390 list...
> i thought it could be possible to lock the v-disk because the performact > toolkit shows > "residend" "locked" and "dasd" page numbers on the vdisk display. Yes, the pages of a VDISK life in the z/VM paging subsystem and rmay reside in main memory, expanded memory, on disk or nowhere... I expect pages are locked only when they are involved in an active I/O. > I already locked the pages of the linux guests because i found it was > fighting for > the storage with the MDC. (i know i can limit the MDC too, but i decided to > lock > the linux guest pages). this reduced paging from several hundred pages per > second > to almost zero. there is only one linux guest in this vm system. Locking pages for performance is normally a Very Bad Idea (TM). Don't do that. If you really want, you could steer CP a bit with SET RESERVED but you probably need to look at other options. Yes, the defaults for CP typically give too much main memory to MDC. My preference is to adjust the BIAS on the SET SRM command but some others set a maximum on MDC. > i am afraid that this fight for storage starts again when i use v-disk for > linux swap (V-DISK vs MDC) MDC is not effective for swap because Linux will normally not read a page a 2nd time. Why do you think you have a "fight" for memory? > Whats the best practice for this? limit MDC size so there is enough "free" > storage for the v-disk? You should probably limit MDC in main memory by a maximum or with a bias. Set the maximum MDC for XSTORE at 0M. > While i am on this: what is the recommendation for the linux swap size? same > as linux storage size? half of > linux storage size? That number is a myth. From what I know it stems from the days where a bug in BSD prevented you from having more swap space than half the memory size, so you'd aim for the maximum. What you want is sufficient "memory" (virtual machine plus swap) to allow the concurrent processes to allocate virtual memory. The tuning option you have is to decide what portion of memory you allocate as virtual machine size. This really depends on the application workload and the importance (and somewhat on the physical resources that you have). You probably need to measure that for each type of system and adjust accordingly. YMMV I know people who run their 1G virtual machine with 16G of swap space. Rob -- Rob van der Heij rvdheij @ gmail.com Velocity Software, Inc
