Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Performance Practices for vSphere 6

Performance Practices for vSphere 6

Silicon Valley VMUG User Conference

99943c4dd162771ea10a70cd53984204?s=128

Nick Marshall

April 15, 2015
Tweet

Transcript

  1. © 2015 VMware Inc. All rights reserved. Nick Marshall Integration

    Architect VMware Performance Practices for vSphere 6
  2. CONFIDENTIAL Who is this guy? Nick Marshall – Author: Mastering

    vSphere – Blog: NickMarshall.com.au – Twitter: @NickMarshall9 – Community: AutoLab, vBrownBag 2
  3. CONFIDENTIAL Agenda • Conquering Performance • vSphere 6 Performance Features

    & General Recommendations • Performance Troubleshooting • Resources 3
  4. Conquering Performance

  5. CONFIDENTIAL Virtual Machine Scalability • Virtualize 99.99% of workloads today

    5 VMware
 vSphere 5.5 1mm+ IOPS >80Gb/s HW v10 1TB RAM 64 VCPUs VMware
 vSphere 6 HW v11 4 TB RAM 128 VCPUs 1mm+ IOPS >80Gb/s
  6. CONFIDENTIAL Low Latency Storage IO • 1mm IOPS, >2ms latency,

    8kb block, 32 OIO’s 6 Reference: www.vmware.com/files/pdf/1M-iops-perf-vsphere5.pdf
  7. CONFIDENTIAL Low Latency Network IO • Latency features reduce overhead

    to near native 7 Reference: http://www.vmware.com/files/pdf/techpaper/latency-sensitive-perf-vsphere55.pdf
  8. CONFIDENTIAL The Worlds First TPC-VMS Benchmark Result • Compliant and

    audited by a 3rd party. • While not a direct comparison, you can see how database consolidation scenarios could achieve near native capabilities on the same hardware (>99%). 8 Reference: http://blogs.vmware.com/vsphere/2013/09/worlds-first-tpc-vms-benchmark-result.html OLTP Instance1 OLTP Instance2 OLTP Instance3 HP Proliant DL385 G8
  9. CONFIDENTIAL Virtualized Hadoop • 12% better performance than native for

    TeraSort 9 Reference: http://blogs.vmware.com/performance/2015/02/virtualized-hadoop-performance-vsphere-6.html
  10. vSphere 6 Performance Features & General Recommendations

  11. vCenter – New Features • 10x Improvement in Operational Latencies,

    2x Improvements in Concurrency Lots of effort spent improving vCenter performance to support greater churn and responsiveness • Windows and Appliance Feature Parity Feature and performance no longer limiting which vCenter model to implement • Web Client Performance Improved Examples: Login 13x faster, Right click action 4x faster, Just try it… vSphere 5.5 vSphere 6.0 32 Hosts per Cluster 64 Hosts per Cluster 4000 Virtual Machines per Cluster 8000 Virtual Machines per Cluster 320 CPUs per Host 480 CPUs per Host 4 TB RAM per Host 6 / 12 TB RAM per Host 512 Virtual Machines per Host 1024 Virtual Machines Per Host
  12. vCenter – Recommendations • Web Browser Selection Important Firefox slowest,

    Chrome fastest, IE11 very close 2nd • Database Performance Critical vCenter experience most impacted by database performance, ensure proximity and speed • Place vCenter on Tier 1 Storage Placing the vCenter virtual machine on low latency storage will improve performance and experience • Don’t Change Statistics Levels Change only as necessary, short intervals, as it places a large demand on vCenter and the DB • JVM Sizing vCenter 6 includes a built-in dynamic memory reconfiguration process that automatically runs at startup vCenter 5.5 or older: KB2021302
  13. Compute & Memory – New Features • 128 vCPU’s Virtual

    machines can now scale to 128 vCPUs supporting larger applications and databases • 4TB RAM Virtual machines can now scale to 4 TB RAM better supporting things like in-memory databases • vNUMA and Memory Hot-Add Memory hot added to a virtual machine will now be distributed evenly across vNUMA nodes
  14. Compute & Memory – Recommendations (1/2) • Rightsize, Rightsize, Rightsize

    Spend effort on rightsizing workloads for vCPU count and assigned memory • Size VM into pNUMA Node if Possible Doing this will reduce the potential for remote memory access and/or thread migration • Don’t use vCPU Hot-Add As it disables vNUMA and presents the virtual machine with UMA topology • Select High Performance in BIOS of vSphere Selecting anything else will save power but does potentially induce compute latency • Enable Hyper-Threading vSphere understands and uses Hyper-Threading to its advantage
  15. Compute & Memory – Recommendations (2/2) • Watch Memory Overcommit

    Overcommit provides consolidation value at risk of performance during shortages • Do NOT Use ‘Active Memory’ in a Vacuum Active Memory is more a ‘rate’ counter than a ‘capacity’ counter, temper it with other counters like ‘Consumed’ or use vROPs
  16. Compute & Memory – Technical Resources • Whitepaper: The CPU

    Scheduler in VMware vSphere 5.1 http://www.vmware.com/resources/techresources/10345 • Lab: vSphere Performance Optimization http://labs.hol.vmware.com/HOL/#lab/1474
  17. Network – New Features • NetIOC v3 Reserve bandwidth to

    guarantee service levels • Host-Wide Performance Tuning Engine 10% higher consolidation ratios with web farm use case • vmxnet3 LRO improvement 15-20% improvement in receive throughput and efficiency for Windows
  18. Network – Recommendations • Use vmxnet3 Guest Network Driver Very

    efficient and required for maximum performance • Evaluate Disabling Interrupt Coalescing Default mechanism may induce small amounts of latency in favor of throughout, evaluate disabling it as cost today is negligible • Jumbo Frames Provide Value While challenging to enable end-to-end sometimes they provide value to high throughput functions like VSAN, vMotion and NAS • It’s a 10Gb World 1Gb saturation is real, more bandwidth required today, especially in light of VSAN, MonsterVM vMotion • Use Latency Sensitivity ‘Cautiously’ While it can reduce latency and jitter in the 10us use case, it comes at a cost with core reservations, etc
  19. Network – Technical Resources • Best Practice for Performance Tuning

    of Latency-Sensitive Workloads http://www.vmware.com/resources/techresources/10220 • Leveraging NIC Technology to Improve Performance https://www.vmware.com/resources/techresources/10450
  20. Storage – New Features • Storage Stack Optimizations Effort spent

    reducing overhead and increasing capabilities to best leverage flash storage Examples: Samsung NVMe 240k -> 710k IOPS, EMC XtremSF 200k -> 670k IOPS • VSAN 6.0 7 Million IOPS, <2 ms Latency • VVOLs Performance the same or better as previous forms of storage integration
  21. Storage – Recommendations • Use Multiple vSCSI Adapters Allows for

    more queues and I/O’s in flight • Use pvscsi vSCSI Adapter More efficient I/O’s per cycle • Don’t Use RDM’s Unless needed for shared disk clustering, no longer a performance advantage • Leverage Your Storage OEM’s Integration Guide They provide necessary guidance around items like multi-pathing
  22. Performance Troubleshooting

  23. Define the Performance Issue • Understand Application Function & Architecture

    At a minimum know what your application does and what it’s dependent on. • Select Application KPIs Application performance must be measured using an application counters (tps, response time, etc) and not virtual resource consumption. • Define Success Criteria With your app owner, define at what level the application KPI’s must be to consider it performant. • Comparisons must be Apples-to-Apples Any changes to infrastructure (physical or virtual) create comparison challenges. • Now the Gap is Identified, Begin Troubleshooting With an understanding of the requirements and current deficiency, you can now begin to investigate and/or tune.
  24. Use the Right Tool • esxtop 2 sec data points,

    VERY granular, not scalable across hosts • vCenter Performance Charts 20 sec data points, okay real-time data, poor history, recommend vROPs • vRealize Operations 5 min data points, very scalable, best starting view • VSAN Observer Most detailed tool to troubleshoot VSAN related performance • 3rd Party Ensure you know what the counters mean and their sample rate
  25. Suggested Methodology Storage Guest CPU Memory Network What are my

    config/tuning options? Change & re- test Acceptable? yes no
  26. Storage: What’s important in the stack VMkernel Guest I/O Drivers

    File System Virtual SCSI File System Application K D G Windows Device Queue R = Perfmon Physical Disk “Disk Secs/transfer” R A K = ESX Kernel G = Guest Latency A = Application Latency D = Device Latency S S = Windows Physical Disk Service Time
  27. Storage: Key Indicators • Device Latency Average (DAVG) This is

    the latency seen at the device driver level. It includes the round-trip time between the HBA and the storage. Investigation Threshold: 10-15ms, lower is better, some spikes okay • Kernel Latency Average (KAVG) This counter tracks the latencies of IO passing thru the Kernel Investigation Threshold: 1ms • Guest Latency Average (GAVG) This is the latency seen at the guest level. It is effectively DAVG + KAVG. Needed for network attached storage. Investigation Threshold: 10-15ms, lower is better, some spikes okay
  28. CPU: Key Indicators • Ready (%RDY) % time a vCPU

    was ready to be scheduled on a physical processor but couldn’t due to processor contention Investigation Threshold: 10% per vCPU • Co-Stop (%CSTP) % time a vCPU in an SMP virtual machine is “stopped” from executing, so that another vCPU in the same virtual machine could be run to “catch-up” and make sure the skew between the two virtual processors doesn’t grow too large Investigation Threshold: 3% • Used (%USED) Make sure the VM is not oversized.
  29. Memory: Key Indicators • Balloon driver size (MCTLSZ) the total

    amount of guest physical memory reclaimed by the balloon driver Investigation Threshold: 1 • Swapping (SWCUR) the current amount of guest physical memory that is swapped out to the ESX kernel VM swap file. Investigation Threshold: 1 • Swap Reads/sec (SWR/s) the rate at which machine memory is swapped in from disk. Investigation Threshold: 1
  30. Network: Key Indicators • Transmit Dropped Packets (%DRPTX) The percentage

    of transmit packets dropped. Investigation Threshold: 1 • Receive Dropped Packets (%DRPRX) The percentage of receive packets dropped. Investigation Threshold: 1
  31. Resources

  32. Andreas Lesslhumer www.running-system.com vSphere 6 ESXTOP quick Overview for Troubleshooting

    ESXTOP Command overview For changing to the different views type: m Memory c CPU n Network i Interrupts d Disk Adapter u Disk Device v Disk VM p Power states x vsan f for add/remove fields V show only virtual machine instances 2 highlight a row scrolling down 8 highlight a row scrolling up o change field order k kill a world e expand/rollup (where available) spacebar: refresh screen s 2: refresh screen every two seconds CPU c – Fields: D F Network n – Fields: A B C D E F K L Memory m – Fields: B D J K Q Disk d – Fields: A B G J VSAN x NUMA m (change to memory view) – Fields: D G Used-by/Team-PNIC: provide information what physical NIC a VM is actually using. %DRPTX, %DRPRX: Dropped Packages transmitted/Dropped Packages received. Values larger 0 are a sign for high network utilization average memory overcommitment for the last one, five and 15 minutes Memory State: high enough free memory available (normal TPS cycles) clear <100% of minFree: ESXi actively calls TPS to collapse pages soft <64% of minFree: Host starts to swap, compress + TPS / no more ballooning low <16% of minFree: ESXi blocks VMs from allocating more RAM + swapping/ compression until it moves back in the hard state. How to calculate minFree: minFree depends on the host memory configura- tion: for the first 28 GB RAM minFree = 899 MB + 1% from the remaining RAM Eg. a host with 100 GB RAM: 899 MB +720 MB (1% of 72 GB RAM) = minFree 1619MB MCTLSZ: Amount of guest physial memory (MB) the ESXi Host is reclaiming by ballon driver. A reason for this is memory overcommitment. DAVG: Latency at the device driver level Indicator for storage performance troubles NMN: Numa Node where the VM is located NRMEM: VM Memory (in MB) located at remote Node NLMEM: VM Memory (in MB) located at local Node N%L: Percentage of VM Memory located at the local NUMA Node. If this value is less than 80 percent the VM will experience performance issues. ABRTS/s: Commands aborted per second If the storage system has not responded within 60 seconds VMs with an Windows Operating System will issue an abort. Resets/s: number of commands reset per second KAVG: Latency caused by VMKernel Possible cause: Queuing (wrong queue depth parameter or wrong failover policy) GAVG: GAVG = DAVG + KAVG CPU load average for the last one, five and 15 minutes %CSTP: This value is interesting if you are using vSMP virtual machines. It shows the percentage of time a ready to run VM has spent in co-deschedule state. If value is >3 decrease the number of vCPUs from the VM concerned. %USED: CPU Core cycles used by a VM. High values are an indicator for VMs causing performance problems on ESXi Hosts. %SYS: Percentage of time spent by system to process interrupts and to perform other system activities on behalf of the world. Possible cause: maybe caused by high I/O VM %VMWAIT: percentage of time a VM was waiting for some VMkernel activity to complete (such as I/O) before it can continue. Includes %SWPWT and “blocked”, but not IDLE Time (as %WAIT does). Possible cause: Storage performance issue | latency to a device in the VM configuration eg. USB device, serial pass-through device or parallel pass-through device %RDY: Percentage of time a VM was waiting to be scheduled. If you note values between five and ten percent take care. Possible reasons: too many vCPUs, too many vSMP VMs or a CPU limit setting (check %MLMTD) Note: for SMP VMs with multiple vCPUs ESXTOP accumulate %rdy for all vCPUs, resulting in higher values. If you want to see the values for each dedicated vCPU, press “e” to Expand/Rollup CPU statistics and insert the GID of the VM you want to analyse. %MLMTD: Counter showing percentage of time a ready to run vCPU was not scheduled because of a CPU limit setting. Remove limit for better performance. %SWPWT: Counter showing how long a VM has to wait for swapped pages read from disk. A reason for this could be memory overcommitment. Pay attention if %SWPWT is >5! SWCUR: Memory (in MB) that has been swapped by VMKernel. Possible cause: memory overcommitment. SWR/s, SWW/s: Rate at which the ESXi Host is writing to or reading from swapped memory. Possible cause: memory overcommitment. CACHEUSD: Memory (in MB) compressed by ESXi Host ZIP/s: Values larger 0 indicate that the host is actively compressing memory. UNZIP/s: Values larger 0 indicate that the host is accessing compressed memory. Reason: memory overcommitment. ROLE READS/s Name of VSAN DOM Role. Number of read operations completed per second. MBREAD/s WRITE/s Megabytes read per second. Number of write operations completed per second. MNWRITE/s RECOWR/s MBRECOWR/s SDLA AVGLAT Megabytes written per second. Number of recovery write operations completed per second. Megabytes written per second for recovery Standard deviation of latency in millisecs for read, write and recovery write. Average latency in millisecs for read, write and recovery write. Copyright © 2015 running-system.com Designed By: Andi Lesslhumer | Version 6.0 running-system.com @ lessi001 > _1 > _1 > _1 > _1 > _1 > _1 > _1 > _1 > _25 > _25 > _3 > _25 <80 > _5 > _1 > _3 >10 >10 100
  33. CONFIDENTIAL Resources VMware’s Performance – Technical Whitepapers http://www.vmware.com/resources/techresources/cat/91,96 VMware’s Tech-Marketing

    Performance Blog http://blogs.vmware.com/vsphere/performance/ VMware’s Perf-Eng Blog (VROOM!) http://blogs.vmware.com/performance Performance Community Forum http://communities.vmware.com/community/vmtn/general/performance VMware Performance Links – Master List https://communities.vmware.com/docs/DOC-25253 Virtualizing Business Critical Applications http://www.vmware.com/solutions/business-critical-apps/ 33
  34. CONFIDENTIAL Resources Performance Best Practices http://www.vmware.com/pdf/Perf_Best_Practices_vSphere5.0.pdf http://www.vmware.com/pdf/Perf_Best_Practices_vSphere5.1.pdf http://www.vmware.com/pdf/Perf_Best_Practices_vSphere5.5.pdf vSphere 6.0

    coming soon! Troubleshooting Performance Related Problems in vSphere Environments http://communities.vmware.com/docs/DOC-19166 (vSphere 5) http://communities.vmware.com/docs/DOC-23094 (vSphere 5.x with vCOps) 34
  35. CONFIDENTIAL Resources Virtualizing Microsoft Business Critical Applications on VMware vSphere

    by: Matt Liebowitz, Alexander Fontana vSphere High Performance Cookbook by: Prasenjit Sarkar Troubleshooting Storage Performance By: Mike Preston VMware vSphere Performance: Designing CPU, Memory, Storage, and Networking for Performance- Intensive Workloads By: Matt Liebowitz, Christopher Kusek, Rynardt Spies Virtualizing SQL Server with VMware: Doing IT Right By: Jeff Szastak, Michael Corey, Michael Webster Virtualizing Oracle Databases on vSphere By: Don Sullivan, Kannan Mani VMware vRealize Operations Performance and Capacity Management By: Ewan ‘e1’ Rahabok 35
  36. CONFIDENTIAL Resources VMware Hands-On-Labs http://labs.hol.vmware.com/ HOL-SDC-1404: vSphere Performance Optimization –

    This has always been one of the most popular labs and has content for both the beginner and the advanced vSphere Administrator. You can learn more about the basics of vSphere Performance or delve into esxtop, or vNUMA. http://labs.hol.vmware.com/HOL/#lab/1474 36
  37. Thank You