Typical command line examples
The following examples demonstrate a few different scenarios in which you might want to use Performance Validator via the command line.
To run 32 bit performance validator run C:\Program Files (x86)\Software Verify\Performance Validator x86\performanceValidator.exe
To run 64 bit performance validator run C:\Program Files (x86)\Software Verify\Performance Validator x64\performanceValidator_x64.exe
Example 1 - running a session (native or .Net)
This example starts the application (native or .Net), showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and some tabs are refreshed.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
performanceValidator_x64.exe -program "c:\myProgram.exe" -saveSession "c:\myResults\session1.pvm_x64" -displayUI -refreshStatistics -refreshAnalysis -refreshCallTree
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\myProgram.exe" |
The target program to launch |
-saveSession |
"c:\myResults\session1.pvm_x64" |
After the application finishes, the session should be saved in this file |
-displayUI |
Show the user interface during the performance test |
|
-refreshStatistics |
Main data tabs should be refreshed when the test completes, including the Summary Results |
|
-refreshAnalysis |
||
-refreshCallTree |
Performance Validator will be left open at the Call Tree tab. |
Example 2 - running a session (native or .Net) and exiting
This example starts the application (native or .Net), showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and Performance Validator exits.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
performanceValidator_x64.exe -program "c:\myProgram.exe" -saveSession "c:\myResults\session2.pvm_x64" -hideUI
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\myProgram.exe" |
The target program to launch |
-saveSession |
"c:\myResults\session2.pvm_x64" |
After the application finishes, the session should be saved in this file |
-hideUI |
Hide the user interface during the performance test and close the user interface when the test application finishes. |
Example 3 - running a session (.Net Core, Self Contained)
This example starts a .Net Core application, showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and some tabs are refreshed.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
performanceValidator_x64.exe -program "c:\myDotNetCoreApp.exe" -dotNetCoreLaunchType SelfContained -saveSession "c:\myResults\session3.pvm_x64" -displayUI -refreshStatistics -refreshAnalysis -refreshCallTree
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\myDotNetCoreApp.exe" |
The target program to launch |
-dotNetCoreLaunchType |
SelfContained |
The .Net Core program is self contained |
-saveSession |
"c:\myResults\session3.pvm_x64" |
After the application finishes, the session should be saved in this file |
-displayUI |
Show the user interface during the performance test |
|
-refreshStatistics |
Main data tabs should be refreshed when the test completes, including the Summary Results |
|
-refreshAnalysis |
||
-refreshCallTree |
Performance Validator will be left open at the Call Tree tab. |
Example 4 - running a session (.Net Core, Framework Dependent)
This example starts a .Net Core application, showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and some tabs are refreshed.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
performanceValidator_x64.exe -program "c:\dotNetCoreApp.dll" -dotNetCoreLaunchType FrameworkDependent -saveSession "c:\myResults\session3.pvm_x64" -displayUI -refreshStatistics -refreshAnalysis -refreshCallTree
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\dotNetCoreApp.dll" |
The target program to launch with the .Net runtime |
-dotNetCoreLaunchType |
FrameworkDependent |
The .Net Core program is framework dependent |
-saveSession |
"c:\myResults\session4.pvm_x64" |
After the application finishes, the session should be saved in this file |
-displayUI |
Show the user interface during the performance test |
|
-refreshStatistics |
Main data tabs should be refreshed when the test completes, including the Summary Results |
|
-refreshAnalysis |
||
-refreshCallTree |
Performance Validator will be left open at the Call Tree tab. |
Example 5 - running and comparing a session
Add the following to the first example to load a previous session, and after the application has finished and this session saved and exported as HTML, compare it with the loaded session, saving the results:
-directory "c:\testarea" -sessionLoad "c:\myResults\session1.pvm_x64" -compareByParentTime -exportAsHTML "c:\myResults\session2.html" -sessionCompareHTML "c:\myResults\comparison_1_2.html"
Option
|
Argument |
Description |
-directory |
"c:\testarea" |
Set the working directory in which the program is executed |
-sessionLoad |
"c:\myResults\session1.pvm_x64" |
Loads this previously saved session into the session manager |
-compareByParentTime |
The loaded session is to be compared with the newly recorded session recorded after the application has terminated, using parent function timings as the basis for comparison |
|
-exportAsHTML |
"c:\myResults\session2.html" |
The recorded session should be saved here in HTML format |
-sessionCompareHTML |
"c:\myResults\comparison_1_2.html" |
The comparison results should be saved here in HTML format |
