Login VSI (website) is the industry standard load testing tool for virtualized desktop environments. Login VSI can be used to test the performance and scalability of every Windows based virtual desktop solution such as: Citrix XenApp, VMware Horizon View,
Microsoft Remote Desktop Services, Citrix XenDesktop or any other VDI solution.

The output of the LoginVSI test contains information about the official workload’s response times, for example “Notepad File Print” or “File Copy Text Share”. But it does not contain any information about the time a step takes or CPU/Memory usage during this stage. The Windows Performance Analyzer (Xperf) can give an insight of these values and with Xperf integration it is possible to measure the time it takes for a step to complete (when you set markers).

Integrating Xperf into LoginVSI requires modifying the workload and this can only be done using the Pro version of LoginVSI.
Xperf uses a small amount of system resources so it’s better to use it to compare markers between different systems then use it during a stresstest. 

Xperf is part of Windows Assessment and Deployment Kit (Windows ADK) which can be downloaded from here (4GB). The Windows Performance Analyzer self are 280 MB.

Extract the content by selecting:


Install (it only extracts the files) the WPTx86-x86_en-us.msi or the WPTx64-x86_en-us.msi on the target (where the sessions will be started, for example the XenApp server).  
Xperf requires Administrative rights to start.Add the LoginVSI group (with the user accounts) to the local Administrators group on the target.  
Move the folder “C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit” to “C:\Xperf”  
Create a folder C:\Xperf\Traces  
Create a new CMD file called Start.cmd in the C:\Xperf\Traces folder  
Open the Start.cmd file in a editor like Notepad  
Enter the following command line:The first step is to specify what Actions of Xperf we want to use.Remember; the more Actions you select, the larger the size of the trace file will be. “C:\xperf\xperf.exe” -on PROC_THREAD+LOADER+DISK_IO+HARD_FAULTS+DPC+INTERRUPT+CSWITCH+PERF_COUNTER+MEMORY+FOOTPRINT+VIRT_ALLOC+MEMINFO+VAMAP+SESSION+REFSET+

MEMINFO_WS+NETWORKTRACE -f C:\Xperf\Traces\Trace-%username%.etl -buffersize 1024

Save the Start.cmd file  
Open the Login VSI Management Console and click on Workload, Customization. image
Click on the workload where Xperf will be integrated, for example Medium.
Click on Edit
Add the code:# Start Xperf
App_Start(“Xperf”, “”, “C:\xperf\traces\Start.cmd”, “”, “”)
VSI_Sleep(2)This will start the trace
The next step is to create Markers when a important step is started.For example:# Measure pre-scripts
App_Start(“Xperf1”, “C:\Xperf\”, “xperf.exe”, ” “, ” “, “”, “-m PreScriptsStart”)
After a step has been finished there needs to be a Marker to finish the step.For example:# Measure pre-scripts
App_Start(“Xperf2”, “C:\Xperf\”, “xperf.exe”, ” “, ” “, “”, “-m PreScriptsStop”)
Repeat the Marker step for every action you want to measure.Make sure to increase the number afterXperf. For example Xperf11, Xperf12 etc..  
After the Workload has been finished, the trace needs to be stopped. At the bottom of the Workload.Enter the following code:# Stop Xperf
App_Start(“Xperf11”, “C:\Xperf\”, “xperf.exe”, ” “, ” “, “”, “-stop”)
Save the workload and start the LoginVSI Test.  
When finished, open the C:\Xperf\Traces folder on the server there is a Trace file called: Trace-%UserName%.etl  
Start C:\xperf\xperfview.exeClick on File, Open and select the trace file from the C:\Xperf\Traces folder  
Click on the arrow on the left and select the Marks checkbox  
Now you can select Actions to display.For example CPU or Memory usage and see how much resources were used during a Step.In the example on the right it shows the CPU usage during Outlook. image
It’s also possible to see how long a step took by selecting the fist Marker triangle and drag to the second triangle.In the example on the right it took 8.1 seconds to start Adobe. 1


Can’t get the solution to work? Contact me and let me do the trick.






Comments are closed