Performance benchmarking and analysis is important to understand key server metrics at both idle and busy time periods. With a good benchmark it makes it possible to properly scale an environment and look for potential performance issues that may arise during usage.
This document is a starting guide to benchmarking XenApp 6.x on Windows Server 2008R2 using Perfmon and the Performance Analysis of Logs (PAL) tool.
Windows Server 2008 R2
XenApp 6.x
Performance Monitor
Performance Analysis of Logs (PAL)
Performance Monitor Wizard (Perfwiz) tool assists in configuring common Perfmon counters for Terminal Services and Exchange. The tool is not supported on Windows Server 2008. Fortunately, 2008 easily configures custom data collector sets starting with a template.
Launch Perfmon, Start > Run > Perfmon.
Expand Data Collector Sets.
Right-click User Defined, select New > Data Collector Set.
Enter a Name for the Data Collector Set (Example: XenApp Performance).
Ensure Create from a template is selected and click Next.
Select System Performance and click Next.
Enter Root Directory where data will be saved and click Next.
Run as Default and click Finish.
This template adds a number of important performance counters. The next step is to add the XenApp related performance counters.
Right-click Performance Counter,Select Properties in the Data Collect Set (XenApp Performance).
Click Add.
Select the following from the Available Counters list:
Right-click XenApp Performance (User Defined Data Collector Set) and select Properties, if you wish to define a schedule (Preferred to benchmarking).
Click Start from the toolbar to begin the Data Collector Set.
The Performance Analysis of Logs (PAL) tool is available as a free download from CodePlex. PAL is a Powershell tool that will output the data it consumes into a nice HTML file that can be viewed with a browser.
Number of Processors
ThreeGBSwitch (should be false for 2k8r2)
SixtyFourBit (should be true for 2k8r2)
Total Memory
Raid5Drives
Raid1Drives
Output options can be left as default, select Next.
Select Output Directory and ensure HTML Output is selected, click Next, until Finish.
PowerShell begins executing and when it completes, the browser opens with a detailed report of the data collected.
Note: The analysis of the report is not covered in this guide as results may vary. It is important to have a good baseline under normal conditions before attempting to analyze a performance related issue. Once the baseline is established you can begin looking at Alerts in the reports that are generated to understand any hot spots that might arise.
PAL provides a fine breakdown in the report, starting with the tool parameters, which includes the Analysis Interval.
Some key Citrix metrics are shown including the IMA WorkItem Queue Ready Count, Data Store Failures, and busy XML Threads. Ensure to check Memory Allocations, CPU Resources, Disk and Network usage statistics.