A newer version of this document is available. Customers should click here to go to the newest version.
- Configure Yocto Project*/Wind River* Linux* and Intel® VTune™ Profiler with the Intel System Studio Integration Layer
<span class='codeph'>threading</span> Command Line Analysis
Threading analysis helps identify the cause of ineffective processor utilization and shows where your application is not parallel. One of the most common problems is threads waiting too long on synchronization objects (locks). Performance suffers when waits occur while cores are under-utilized.
Threading analysis combines and replaces the Concurrency and Locks and Waits analysis types available in previous versions of Intel® VTune™ Profiler.
Threading analysis uses user-mode sampling and tracing collection. With this analysis you can estimate the impact each synchronization object has on the application and understand how long the application had to wait on each synchronization object, or in blocking APIs, such as sleep and blocking I/O.
There are two groups of synchronization objects supported by the Intel® VTune™ Profiler:
objects usually used for synchronization between threads, such as Mutex or Semaphore
objects associated with waits on I/O operations, such as Stream
vtune -collect threading [-knob <knobName=knobValue>] [--] <target>
For the most current information on available knobs (configuration options) for the Threading analysis, enter:
vtune -help collect threading
This example shows how to run the Threading analysis on a Linux* myApplication application:
vtune -collect threading -- /home/test/myApplication
When the data collection is complete, do one of the following to view the result:
Use the -report action to view the data from command line.
Use the -report-output action to write report to a .txt or .csv file
Open the data collection result (*.vtune) in the VTune Profiler graphical interface.
Did you find the information on this page useful?