Understand what logical performance services are provided by VMware solutions
From the this blog:
Memory VMware offers the following features to manage the memory efficiently
- Transparent Page Sharing: Shares identical Memory Pages among multiple virtual machines. This feature is active by default and does not impact the performance of the virtual machine.
- **Ballooning: **Controls a balloon driver which is running inside each virtual machine. When the physical host runs out of memory it instructs the driver to inflate by allocating inactive physical pages. The ESX host can uses these pages to fulfill the demand from other virtual machines.
- Memory Compression: Prior to swap memory pages out to physical disks the ESX server starts to compress pages. Compared to swapping, compression can improve the overall performance in an memory overcommitment scenario.
- Swapping: As the last choice the ESX hypervisor starts to swap pages out to physical disks. This is definitely a bad situation as disk are much slower than memory.
Disk Storage I/O Control (SIOC) allows cluster wide control of disk resources. The main goal is to prevent a single VM to use all available disk performance from a shared storage. With SIOC a virtual machine can be assigned a priority when contention arises on a defined datastore.
Network Network I/O Control (NetIOC) enables traffic prioritization by partitioning of network bandwidth among the entire cluster.
Identify and differentiate infrastructure qualities (Availability, Manageability, Performance,Recoverability, Security)
See previous objective
List the key performance indicators for resource utilization
From same blog as above:
Key Performance Indicators According to ITIL, a Key Performance Indicator (KPI) is used to assess if a defined service is running according to expectations. The exact definition of the KPIs differs depending on the area. This objective is about server performance which is typically assessed using the following KPIs: Processor, Memory, Disk, and Network.
Analyze current performance, identify and address gaps when building the logical design
From the APAC BrownBag Session 14 Slide deck:
Using a conceptual design, create a logical design that meets performance requirements.
Let’s say we say that we will have production VMs and development VMs. From the Conceptual design we will just have two different containers that represent each type of a VM. For the Logical Design we will have DRS Resource Pools and Tiered Storage. Here is an example take from a VMware article called “Storage Considerations for VMware vCloud Director”:
Identify performance-related functional requirements based on given non-functional requirements and service dependencies
Let’s say a non-functional requirement is we can only spend $50,000 for our storage needs. This will of course translate to what kind of disks we can afford, SSD Vs. SAS and how many of the disks. Depending on what type and how many disk we buy, we will limited to certain amount of IOPS.
Define capacity management practices and create a capacity plan
From the linked document in the blue print “Proven Practice: Implementing ITIL v3 Capacity Management in a VMware environment”:
A key goal for Capacity management is to provide value to the business; this can be done to great effect using VMware and consolidation. Using consolidation it is possible to reduce the number of physical servers and to utilize those reduced physical servers at a more optimal rate. … … Within Business Capacity Management we are looking to provide metrics to demonstrate our value to the business and whether we are meeting their requirements. The sort of metrics we could look at producing are:
- % reduction in physical estate
- % reduction in power consumption (useful as documented evidence in obtaining any environmental standard e.g. ISO14001)
- % cost reduction in maintenance contracts
.. .. For a consolidation exercise we would look to use a tool such as VMware Capacity Planner that will analyze the current utilization of your server estate and determine your optimum consolidation requirements.
Make sure to define what the capacity is of the current environment.
Incorporate scalability requirements into the logical design.
Determine performance component of SLAs and service level management processes
From the same article as mentioned in the previous objective:
As we know, the response time of a service/application is a key performance metric and it is used to determine the end user experience of using a service that conventional metrics like CPU utilization, memory consumption, etc won’t necessarily show.
Data relating to the response time of a service can be difficult to obtain, but is critical to determining how a service is performing. This sort of data will also become more important when we look at consolidating servers into a VMware environment as the resource limits that are applied when viewing the hardware as a whole will have a greater impact.
Figure 2 shows the relationship between utilization and the response time. As you can see the relationship isn’t a linear one; as the utilization starts to get closer to 100% the response time starts to increase greatly. As discussed previously this issue will become more apparent as the number of Virtual Machines hosted increases and will need perhaps more management than if the servers were physical. The key to managing this is to ensure accurate collection of the response time. .. .. If you currently use a terminal emulation tool to graphically recreate a number of standard user steps to calculate the response time, then you may not need to alter the capture at all, but remember that the data captured prior to implementation will then provide a useful comparison from the SLA perspective. It will also provide a valuable business metric as to the benefits of moving to a VMware environment i.e. “We have consolidated Service A to VMware and it has reduced the user response time by 25%”.
For Troubleshooting Performance issues, I would suggest to read the following: