Optimize Oracle On VMware (Sep 2011)
Download as PPTX, PDF4 likes3,053 views
This document discusses optimizing Oracle databases that run on VMware virtual machines. It covers VMware's memory, CPU, and I/O resource management and provides recommendations for configuration. Key points include using memory reservations to avoid swapping, allocating enough vCPUs while avoiding overprovisioning, dedicating storage and enabling Storage I/O Control for I/O performance. Oracle RAC support on VMware requires Oracle 11.2.0.2 or higher.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Optimize Oracle On VMware (Sep 2011) (20)
Ad
More from Guy Harrison (16)
Recently uploaded (20)
Optimize Oracle On VMware (Sep 2011)
- 1. Optimize Oracle RDBMS on VMwareGuy HarrisonDirector, R&D [email protected]@guyharrison
- 3. AgendaMotivations for VirtualizationVMware ESX resource management:MemoryCPUIOParavirtualization (OVM) vs Hardware Assisted Virtualization (ESX)RAC on VMware
- 5. Resistance to Database virtualization
- 6. DB virtualization is happening
- 8. Oracle virtualization is lagging....
- 10. Managing ESX memoryESX can âovercommitâ memorySum of all VM physical memory allocations > actual ESX physical memoryMemory is critical to Oracle server performanceSGA memory to reduce datafile IOPGA memory to reduce sort & hash IO ESX uses four methods to share memory:Memory Page SharingâBallooningâMemory compressionESX swappingDBA needs to carefully configure to avoid disaster
- 11. Configuring VM memoryVMs Compete for memory in this rangeRelative Memory Priority for this VMMaximum memory for the VM (dynamic)Minimum Memory for this VM
- 13. ESX and VM memoryESX SwapESX swapVMESX virtual memory Effective VM physical memory ESX physical memoryVM virtual memory
- 14. ESX BallooningESX SwapESX swapVmmemctlâballoonâVMESX virtual memory Apparent VM physical memory Effective VM physical memory ESX physical memoryVM SwapVM Swap
- 15. ESX BallooningAs memory grows, ESX balloon driver (vmmemctl) forces VM to page out memory to VM swapfile
- 16. ESX BallooningInside the VM, paging to the swapfile is observed.The guest OS will determine which pages are paged outIf LOCK_SGA=TRUE, then the SGA should not be paged.
- 17. ESX SwappingESX SwapESX swapESX virtual memory VMEffective VM physical memory ESX physical memoryVM virtual memory
- 18. ESX SwappingESX SwapESX swapVMApparent VM physical memory Effective VM physical memory ESX virtual memory ESX physical memory
- 19. ESX SwappingESX swaps out VM memory to ESXswapfile
- 20. ESX SwappingWithin the VM, swapping cannot be detected.ESX will determine which memory pages go to diskParticularly occurs when VMware tools are not installedEven if LOCK_SGA=TRUE, SGA memory might be on disk
- 21. Avoiding Ballooning and swappingmemory reservations help avoid ballooning or ESX swapping
- 22. ESX memory managementMemory page sharing Multiple VMs can share an identical page of memory (Oracle code pages, etc) Memory compression (new in vSphere 4.1)Pages are compressed and written to cache rather than to diskSwapping is more expensive than ballooningSlower to restore memoryOS and Oracle get no choice about what gets pagedâDouble pagingâ can occur â guest and ESX both page a block of memory
- 23. Ballooning vs. Swapping Swingbench workload running on Oracle database â from VMWare whitepaper: http://www.vmware.com/files/pdf/perf-vsphere-memory_management.pdf
- 24. VMware memory recommendations Paging or swapping of PGA or SGA is almost always a Very Bad Thingtm.Use memory reservations to avoid swapping or ballooningInstall VMware tools to allow ballooning instead of swappingSet Memory reservation = PGA+SGA+process OverheadBe realistic about memory requirements:In physical machines, we are used to using all available memoryIn VM, use only the memory you need, freeing up memory for other VMsOracle advisories (or Spotlight) can show you how much memory is neededReduce VM reservation and Oracle memory targets in tandem to release memory
- 27. ESX CPU management If more virtual CPUs than ESX CPUs, then vCPUs will sometimes wait for physical CPUTime âstopsâ inside the VM when this occurs For multi-CPU VMs, itâs (nearly) all or nothing. A vCPU can be in one of three states:Associated with an ESX CPU but idleAssociated with an ESX CPU and executing instructionsWaiting for ESX CPU to become available Shares and reservations determine which VM wins access to the ESX CPUs
- 28. Configuring VM CPU VMs compete for CPU in this rangeShares determine relative CPU allocated when competing
- 29. CPU utilization VMâCPU Readyâ is the amount of time VM spends waiting on ESX for CPU Inside the VM, CPU stats can be misleading
- 30. SMP for vCPUsESX usually has to schedule all vCPUs for a VM simultaneouslyThe more CPUs the harder this isSome CPU is also needed for ESXMore is therefore not always better(Thanks to Carl Bradshaw for letting me reprint this diagram from his Oracle on VMWare whitepaper)
- 31. ESX CPU performance comparisonsVT enabledVs 2 core 1.8 GHz physical machine
- 32. Programmatic performance NB: Not a benchmark! Just some informal measurements!!
- 34. ESX CPU recommendations Use up to date chipsets and ESX softwareAllocate as few VCPUs as possible to each VMUse reservations and shares to prioritise access to ESX CPUPerformance of CPU critical workloads may be disappointing on older hardwareMonitor ESX Ready time to determine the âpenaltyâ of competing with other virtual machines
- 35. ESX IO managment
- 36. Typical VMWare disk configuration
- 37. IO Resource AllocationDisk shares can be used to prioritize IO bandwidth.This is poorly implemented prior to vSphere 4.1
- 38. Storage IO ControlPrior to vSphere 4.1: disk shares could be used only at the VM level, and only within a single ESX hostvSphere 4.1 Storage IO Control (SIOC):Manages disk share priorities for all VMs attaching to the same datastoreIs triggered by high (âcongestedâ) latencyCan be enabled globally at the datastore levelEnables equitable distribution even when set to defaults
- 40. vSphere 4.1 SIOC
- 41. SOIC wonât make up for a poorly configured IO layout
- 42. Performant VMware disk configuration
- 43. Optimal configuration See âOracle Database Scalability in VMwareÂŽ ESXâ at www.vmware.com/oracleEach virtual disk directly mapped via RDM to dedicated RAID 0 (+1) group 41 Spindles!
- 44. ESX IO recommendationsFollow normal best practice for physical disksAvoid sharing disk workloads Dedicated datastores using VMFS Align virtual disks to physical disks?Consider Raw Device Mapping (RDM)Consider SIOC in vSphere 4.1 If you canât optimize IO, avoid IO:Tune, tune, tune SQLPrefer indexed pathsMemory configurationDonât forget about temp IO (sorts, hash joins)
- 45. Shameless plugs
- 50. Paravirtualizationvs âHardware VirtualizationâVirtualization is not emulation....Where-ever possible, Hypervisor runs native code from OS against underlying hardwareBecause a virtualized operating system is running outside privileged x86 âring 0â, direct calls to hardware need special handling.The three main approaches are:Full Virtualization (VMWare on older hardware)ParaVirtualization (Xen, Oracle VM)Hardware Assisted Virtualization (Intel VT, AMD-V)
- 51. Full virtualization Hardware calls from the VM are handled by the hypervisor by:Catching the calls as they occur at run timeRe-writing the VM image at load time (binary translation)Requires no special hardwareSupports any guest OSRelatively Poor performanceUsed by ESX on older chip-setsVMHypervisorRing 0Hardware
- 52. Hardware Assisted virtualizationIntel VT and AMD-V chips add a âroot modeâ.VMcan issue instructions from non-root Ring 0.CPU can divert these to hypervisorNo changes to OS requiredGood performanceRequires modern chipsetsRoot ModeNon-Root ModeVMHypervisorRing 0Hardware
- 53. ParavirtualizationVM operating system is rewritten to translate device calls to âhypercallsâ
- 54. Hypercalls are handled by a special VM (dom0 in Xen/OVM)
- 55. Good performance but requires modified VM OS
- 56. Xen can use either paravirtualization or hardware assistVM(domU)Ring 0VM(dom0)HypervisorHardware
- 57. RAC and ESX
- 58. Paravirtualization, ESX and RACPrior to 11.2.0.2, Oracle relied on paravirtualized kernels to maintain time synchronization for RAC clusters.From 11.2.0.2 Oracle uses Cluster Time Synchronization Service (CTSS) to maintain clock sync, and this works on ESXTherefore, Oracle supports RAC on Vmware ESX only from 11.2.0.2 onwardsSee Oracle MySupport Note 249212.1
- 59. ReferencesLatest version of this presentation:http://www.slideshare.net/gharriso/optimize-oracle-on-vmware-5271530My blog (www.guyharrison.net ):http://guyharrison.squarespace.com/blog/2010/2/22/memory-management-for-oracle-databases-on-vmware-esx.htmlhttp://guyharrison.squarespace.com/blog/2010/4/9/esx-cpu-optimization-for-oracle-databases.htmlhttp://guyharrison.squarespace.com/blog/2010/7/12/stolen-cpu-on-xen-based-virtual-machines.htmlhttp://www.vmware.com/files/pdf/perf-vsphere-memory_management.pdfhttp://www.vmware.com/files/pdf/Oracle_Databases_on_vSphere_Deployment_Tips.pdfhttp://www.vmware.com/files/pdf/techpaper/VMW-vSphere41-SIOC.pdf
Editor's Notes
- #3: Apologies, Iâm a database type.....Quest is best known for toad, but we also have enterprise monitoring across all levels of the stackIn Melbourne, SQL Navigator + the spotlights. Itâs not a complete co-incidence about the star trek theme.
- #12: As well as total memory to the VM, you can:Adjust memory âsharesâ, which determine priority for this machine when in contention with other machinesReservation: guaranteed (sort of) amount of memory to allocate Limit, if you want to prevent VM from getting all itâs memory Memory reservationsMemory SharesIdle memory taxMemory sharingThe Balloon driver (vmmemctl) ESX swapping