VMWare Performance Tuning by Virtera (Jan 2009)

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    9 Favorites

    VMWare Performance Tuning by Virtera (Jan 2009) - Presentation Transcript

    1. Getting the Most out of Your VMware Environment with Performance Tuning Mike Burke Virtual Infrastructure Practice Director January 2009
    2. What is Performance Tuning?
    3. What is Performance Tuning?
          • Proper planning and design
          • Configuration best practices
          • Operational awareness
      X
    4. Start with the “Four Core” But first!
    5. A Few Questions…
      • How many CPUs per host?
      • How much memory per host?
      • Ratio of memory to CPU?
      4:1 ? 2:1 ? What’s the “Best Practice”?
    6. A Simple Answer
      • “ Best Practices” are subjective
      • Tuning is not a replacement for proper planning
        • Don’t guess – gather the data
      • Know your workloads
        • Are you CPU-bound or memory-bound?
        • Spec hardware based on need
    7. Optimizing CPU
      • More cores are generally better
      • Use vSMP sparingly
        • Consider workload needs
        • Should it be virtualized?
      • Consider vSMP scheduling constraints
        • ESX must schedule all VCPUs at once
        • Re-evaluate 4-CPU candidates
    8. Memory Optimization
      • Generally, more host RAM = better performance
      • Configure a VM’s memory based on the actual need.
      • Tune migrated systems accordingly
      • Be careful over-allocating RAM
      • No swapping!
    9. Advanced Memory Parameters
      • Mem.ShareScanTime
        • Time interval for TPS scanning (60 min)
      • Mem.ShareScanGhz
        • Amount of memory pages to scan per 1Ghz idle cycles (4MB/sec per 1Ghz)
      • Mem.CtlMaxPercent
        • Limits memory reclamation by ballooning (vmmemctl) (65%)
    10. Advanced Memory Parameters
      • Per VM:
      • sched.mem.maxmemctl
        • Max memory reclamation by ballooning (vmmemctl)
      • sched.mem.pshare.enable
        • Enable /disable memory sharing (TPS)
      • sched.swap.persist
        • vSwap persists after power-off
    11. Optimizing Storage
      • Use shared storage
        • Fiber-Channel SAN
        • iSCSI
        • NFS
      • ESX supports dynamic failover…
        • MRU only for Active/Passive
      • … but manual load balancing
        • Provision alternately/accordingly
    12. Optimizing Storage
      • RAID Types
        • Balance performance vs. cost
        • Know your workload
      • Use iSCSI HBA’s on production
        • Offload CPU time to hardware
        • Jumbo frames
    13. Storage Recommendations
      • Tier storage based on need
        • Tier 1 – DMX/Fiber
        • Tier 2 – iSCSI/SATA
        • ISO/Templates – NFS, iSCSI or SATA
      • Tier storage based on environment
        • Split PROD and DEV/UAT
      • Split based on DR plans
        • System, data, swap
        • sched.swap.dir
    14. Storage Recommendations
      • LUN sizing
        • VMs per LUN
        • Average size of disk
        • Remember vSwap and headroom
      • One VMFS per LUN
      • Align VMFS volumes
      • More, smaller LUNs vs. less, larger LUNs
    15. VMFS Recommendations
      • Limit hosts per LUN
        • Locking issues
      • Do not use extents
        • Use SMotion
      • Use RDM’s for disks over a certain size
        • Draw a line in the sand
      • Unload VMFS2 drivers
        • vmkload_mod –u vmfs2
    16. Networking
      • Gigabit only
        • Negotiate auto/auto in most instances
        • Know your settings
      • Four NICs minimum
      • Enable spanning-tree PortFast
    17. Networking
      • Dedicate NICs to iSCSI/NFS
        • Second Service Console interface
      • Software iSCSI load-balancing
        • Only possible with EtherChannel
    18. Networking
      • Always more than one NIC per vSwitch
        • Different physical switches
        • Different transceivers
        • Check PCI addressing for VMNIC ordering
      • Combine Service Console and VMkernel
        • LB at the port group level
        • Add third dedicated to failover
        • Ensure consistency in port usage
      • Security conscious: Isolate VMotion
    19. Networking
      • Place high-I/O VMs on the same:
        • Host
        • vSwitch
        • Port group
    20. HA Recommendations
      • Ensure the Service Console has redundant paths
        • PINGable gateway
        • Alternate source
      • Watch memory over-commitment
      • Understand admission control
        • No strict admission control in 2-node clusters
      • All names/IPs registered in DNS
    21. HA Advanced Parameters
      • das.isolationaddress
        • Address to PING for failure detection
      • das.defaultfailoverhost
        • Which host should be the target of the failover
      • das.failuredetectiontime
        • How long to wait to initiate failure detection
      • das.failuredetectioninterval
        • How long between heartbeats
    22. DRS Recommendations
      • Remember – CPU and Memory only
      • Use affinity rules
        • Specify exempt VMs
        • Place appropriate VMs together
        • Separate conflicting VMs
      • Go Fully-Automated with HA
        • But, conservative migration threshold
    23. A Word on DRS and HA
      • HA relies on reservations to determine available capacity
        • Set at the VM level
      • das.vmMemoryMinMB
        • Catch-all memory reservation to consider when failover occurs
      • das.vmCpuMinMHz
        • Catch-all CPU reservation to consider when failover occurs
      X
    24. Shares, Reservations and Limits
      • Reservations are hard commits
      • Shares are relative priority
      • Limits create sandboxes
    25. General Host Recommendations
      • Mix workloads
        • Better overall utilization
      • Leverage reservations for critical systems
        • Particularly in HA scenarios
      • Limit 3 rd party tools in the Service Console
      • Antivirus
        • If you must, remove /vmfs from scan list
      • Configure NTP
    26. General VM Recommendations
      • Always load VMware Tools
      • Disable peripherals note used
        • COM, LPT, Floppy, etc.
      • Time sync
        • VMware Tools or NTP
      • Disable Sync driver on Terminal Server and Database VMs (vmmemctl)
      • “ Can” screen savers and backgrounds
      • Unmap unused CD-ROMs/ISOs
    27. Questions?
    28. Thanks! Mike Burke Virtual Infrastructure Practice Director [email_address] January 2009
    29. Key Counters
      • CPU Usage
        • (% and MHz)
      • % Ready/CPU Ready
        • ESXTOP/VC, per VM
      • Memory Usage %
      • Memory Consumed
      • Memory Granted
      • Memory Balloon
      • Memory Swap Used
      • Memory Shared
    30. Key Counters
      • Disk Usage (KBps)
      • VMFS Volume Free Space
        • VC database or ESX host directly
      • Network Usage (KBps)
        • Host and per-VMNIC
    31. ESX Host Monitoring
      • Virtual Center
        • Changing graph timescale changes sample size
        • Change collection intervals
        • Increase thread count
      • esxtop
        • Be sure to change modes (c - cpu, d - disk, m - memory)
      • %RDY is a red flag
        • VM’s are spending time in a queue waiting to be scheduled
      • Swapping stats
        • Out of RAM?
      • Consistent CPU times > 80%
        • Need another host?
      • Disk queue lengths
        • Read vs. Write characteristics
        • What disk I/O loads are in competition on the SAN?
    32. Virtual Machine Monitoring
      • Establish a baseline with Performance Monitor
      • Understand what “normal” is before trouble starts
      • What are your SLA’s?
      • What is expected/acceptable performance?
      • Average/Peak CPU Utilization
      • Processor Queue Length
      • Memory Usage
      • Peak Memory Usage
      • Page Faults
      • I/O Reads vs. Write
      • I/O Bytes (Read and Write)
      • Disk Queue Lengths
      • Network Bytes Received/Sent
    33. Generally Speaking…
      • CPU and Memory will be constrained
      • Disk and network saturation uncommon
      • Keep overall CPU utilization under 65%
      • Keep Memory utilization under:
        • 100% for production systems
        • 125% for development/test systems

    + vmugvmug, 10 months ago

    custom

    5464 views, 9 favs, 4 embeds more stats

    VMWare Optimizations and Performance Tuning by VIRT more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 5464
      • 5185 on SlideShare
      • 279 from embeds
    • Comments 0
    • Favorites 9
    • Downloads 0
    Most viewed embeds
    • 275 views on http://www.vmgu.ru
    • 2 views on http://www.vmworld.com
    • 1 views on http://staging.visualcv.com
    • 1 views on http://www.vmworldeurope.com

    more

    All embeds
    • 275 views on http://www.vmgu.ru
    • 2 views on http://www.vmworld.com
    • 1 views on http://staging.visualcv.com
    • 1 views on http://www.vmworldeurope.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories