1. LoadGen
  2. LoadGen Applications
  3. LoadGen Studio

Benchmarking your (VDI) session

LoadGen 2021-Q4 - 5.0.0.7524

LoadGen Flows with Benchmarking actions are not backwards compatible.

With our Q4 release, we bring you our new benchmarking user actions, you can now perform the following actions in your workload so you can establish a baseline for CPU and IO actions based on the amount of time these actions took to complete the result.

The following actions are available:

  • Measure CPU Performance: Calculate x times the y th power of n. This action will benchmark your CPU performance of a Virtual Machine, VDI, or hosted desktop.
  • Measure IO Performance: This function will create x files based on a y size, then you can either read these files or remove them. This action will benchmark your IO performance of a Virtual Machine, VDI, or hosted desktop.
  • Gather System Information: This action will send your Virtual Machine, VDI, or hosted desktop system information to the database.

Measure CPU Performance

This action will measure the CPU Performance by calculating x times the y th power of n. This action will benchmark your CPU performance of a Virtual Machine, VDI, or hosted desktop.

  1. Drag the Measure CPU performance action to your Application Block sequence:
  2. Enter the values into the presented form. In the below example we will use the following formula:  and we will repeat that 2 times.

  1. When running this action in a test the following information will be stored in the User Action database table:
    1. Username: the username of the test user.
    2. Remote server: the machine name of the endpoint the test is running against.
    3. LoadBot: the name of the LoadGen Agent.
    4. Actual Time: the recorded time when the event occurred.
    5. Relative Time: the recorded time (of the start of the test) when the event occurred.
    6. Iteration: in which iteration cycle this event occurred.
    7. Type: always SubtransactionTimeStop, you can create the chart with this filter.
    8. Message: the command of the CPU measurement calculation, in the above example: 2 x (10 to the 6th power) calculation.
    9. Session Time: the recorded time (of the start of the test of this specific user) when the event occurred.
    10. Subtransaction Name: always CPUMeasurement, you can create the chart with this filter.
    11. Subtransaction Time: the time it has taken to perform the action.

Measure IO Performance

Write files

This action will measure the IO Performance by creating x files based on a y size. This action will benchmark your IO performance of a Virtual Machine, VDI, or hosted desktop.

  1. Drag the Measure CPU performance action to your Application Block sequence:
  2. Enter the values into the presented form. In the below example we will create 1,000 files with a size of 1,024 KB. These files will be created in the following folder %TEMP%\LoadGen\IOFiles.
  3. The File IO Write action will create the files, the LoadGen process will keep a handle open during the test users session, so you can perform the File IO Read action with the same file set which was created in the File IO Write action.

  1. When running this action in a test the following information will be stored in the User Action database table:
    1. Username: the username of the test user.
    2. Remote server: the machine name of the endpoint the test is running against.
    3. LoadBot: the name of the LoadGen Agent.
    4. Actual Time: the recorded time when the event occurred.
    5. Relative Time: the recorded time (of the start of the test) when the event occurred.
    6. Iteration: in which iteration cycle this event occurred.
    7. Type: always SubtransactionTimeStop, you can create the chart with this filter.
    8. Message: the command of the File IO measurement calculation, in the above example: 1000 x 1048576 bytes operation.
    9. Session Time: the recorded time (of the start of the test of this specific user) when the event occurred.
    10. Subtransaction Name: always FileIOWrite, you can create the chart with this filter.
    11. Subtransaction Time: the time it has taken to perform the action.

Read files

This action will measure the IO Performance by reading x files based on a y size, the File IO Read action can only work after defining a File IO Write action first. This action will benchmark your IO performance of a Virtual Machine, VDI, or hosted desktop.

  1. Drag the Measure CPU performance action to your Application Block sequence:
  2. Select the File IO Read option. In the below example we already created 1,000 files with a size of 1,024 KB. These files will be created and read from the following folder %TEMP%\LoadGen\IOFiles.
  3. The File IO Write action will create the files, the LoadGen process will keep a handle open during the test users session, so you can perform the File IO Read action with the same file set which was created in the File IO Write action.

  1. When running this action in a test the following information will be stored in the User Action database table:
    1. Username: the username of the test user.
    2. Remote server: the machine name of the endpoint the test is running against.
    3. LoadBot: the name of the LoadGen Agent.
    4. Actual Time: the recorded time when the event occurred.
    5. Relative Time: the recorded time (of the start of the test) when the event occurred.
    6. Iteration: in which iteration cycle this event occurred.
    7. Type: always SubtransactionTimeStop, you can create the chart with this filter.
    8. Message: the command of the File IO measurement calculation, in the above example: Read operation (1000 x 1048576 bytes).
    9. Session Time: the recorded time (of the start of the test of this specific user) when the event occurred.
    10. Subtransaction Name: always FileIORead, you can create the chart with this filter.
    11. Subtransaction Time: the time it has taken to perform the action.

Delete files

This action will measure the IO Performance by reading x files based on a y size, the File IO Read action can only work after defining a File IO Write action first. This action will benchmark your IO performance of a Virtual Machine, VDI, or hosted desktop.

  1. Drag the Measure CPU performance action to your Application Block sequence:
  2. Select the File IO Delete option. In the below example we already created 1,000 files with a size of 1,024 KB. These files will be deleted from the following folder %TEMP%\LoadGen\IOFiles.

Gather System Information

This action will send your Virtual Machine, VDI, or hosted desktop system information to the database.

  1. Drag the Gather System information action to your Application Block sequence:
  2. When running this action in a test the following information will be stored in the User Action database table:
    1. Username: the username of the test user.
    2. Remote server: the machine name of the endpoint the test is running against.
    3. LoadBot: the name of the LoadGen Agent.
    4. Actual Time: the recorded time when the event occurred.
    5. Relative Time: the recorded time (of start of test) when the event occurred.
    6. Iteration: in which iteration cycle this event occurred.
    7. Type: always SendMessage.
    8. Message: the result of the system specifications:
      1. Microsoft Corporation - Virtual Machine
      2. CPU #0 - GenuineIntel - Intel64 Family 6 Model 85 Stepping 4 - Cores: 2 - LogicalCores: 4 - ClockSpeed: 2095
      3. Hyper-Threading enabled: Yes
      4. Total Memory: 16GB
      5. Disk #0: Caption: C: - Description: Local Fixed Disk -  Type: Local Disk - Space: 108.73\126.51GB
      6. Disk #1: Caption: D: - Description: Local Fixed Disk -  Type: Local Disk - Space: 30.91\32GB
    9. Session Time: the recorded time (of the start of the test of this specific user) when the event occurred.
Was this article helpful?
0 out of 0 found this helpful