Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
OSBench.exe enables you to collect timing samples to measure the performance of the kernel by conducting scheduler performance-timing tests. A scheduler performance-timing test measures how much time is required for a basic kernel operation, such as synchronization. An example of synchronization is scheduling a thread that is waiting on an event that has just been set by another thread. Wherever appropriate, the test runs two sets of metrics: thread-to-thread within a process and thread-to-thread across processes. If appropriate, you can apply a stress suite while running the test.
OSBench.exe enables you to determine how long it takes to perform the following tasks:
- Acquire or release a critical section
- Wait or signal an event
- Create a semaphore or mutex
- Yield a thread
- Call system APIs
You can use the following command-line parameters with this tool.
osbench [-all] [-ttest_case] [-list] [-v] [-nnumber] [-maddress]
[-ofile_name] [-h]
The following table shows the command-line parameters used with OSBench.exe.
| Command-line parameter | Description |
|---|---|
| -all | Runs all tests. The default setting is to run only those specified by the -t parameter. |
| -ttest_case | Specifies the identifier of the test case to run. A separate -t parameter is required for each test. |
| -list | Lists test identifiers with descriptions. |
| -v | Indicates verbose output or to show all measurements. The default setting is the summary output only. |
| -nnumber | Specifies the number of samples per test. The default setting is 100. |
| -maddress | Specifies the virtual address to write marker values. The default setting is none. |
| -ofile_name | Sends output to a comma-separated file. The default setting is to send the output to a debugger message window. |
| -h | Displays a Help screen. |
See Also
Real-Time Measurement Tools | OSBench Support
Send Feedback on this topic to the authors