AMS_042909.pptVIP

More Application Availability, Less Work on Weekends So how does Virtual Memory work? What does Virtual Memory give you? Protect Kernel from User processes Protect user processes from each other Run a program that is not all in memory Isolation of processes All processes have the same addresses range Demands: Kernel and User mode bit (switches page tables) Virtual to physical address translation (page table) Interrupts on page fault (CPU and interrupt handlers) Memory pages saved on disk Restartable instructions Virtual Memory Process level Paging LPAR level Paging How to live with paging? Spread paging I/O across many disk spindles 5 second glitch or 0.5 second glitch Disk write caches Please protect paging space What is the problem that needs solving? Solution design, each LPAR: How much memory? Guess “10 GB sounds about right” Policy “every app server gets 8 GB” App vendor recommend “12.5 GB” Add a bit for safety +10% ? It is all a little hit and miss But do they really need that memory? Hard to tell due to AIX optimisation of memory! Can we rebalance memory for real use? YES with AMS AMS – Harvesting and Utilization Dedicated memory Each LPAR owns its memory Un-used memory ? is wasted Over-used memory ? pages to disk ? Manual dynamic memory change is rare Active Memory Sharing – Good Uses Around the World Demands that peak at different times AMS Pre-Requisites POWER6 only Firmware 342* HMC 7.3.4.2* VIOS 2.1.1 AIX 6.1 TL03 ? No AIX 5.3 support PowerVM Enterprise Edition VET activation code for installed machines No 16 MB pages (used by some HPC codes) Shared CPU LPAR only Shared I/O i.e. Pure Virtual I/O LPARs Also supported ? SLES 11, RHEL 6 IBM i V6R1 (via PTF) AMS – Memory Pool machine level Shared Memory Pool Bit like Shared Processor Pool Only one pool (no license issue here) Creating the pool – HMC/IVM machine level Specify size and maximum Specify which VIOS and its paging space Dynamic pool changed Up to max. or the c