Resource Contentions View - Profiler Contention Data
The Resource Contention view lists contention data for the resources that were the source of contention events. A contention event occurs when a function in a thread is forced to wait for access to the resource because a function in another thread has acquired exclusive access to the resource. Each resource is the root node of a call tree that displays the function execution paths that resulted in the contention events.
Function values are based on the instances of the function that occurred in the execution path represented in the call tree.
-
Exclusive values are based on the events that occurred when the function was executing statements in its function body. Events that occurred in functions that were called by the function are not included in exclusive values.
-
Inclusive values are based on the events that occurred when the function or a function called by the function was executing.
|
Column |
Description |
|---|---|
|
Name |
The name of resource or function. |
|
Exclusive Blocked Time |
|
|
Exclusive Blocked Time % |
|
|
Exclusive Contentions |
|
|
Exclusive Contentions % |
|
|
Inclusive Blocked Time |
|
|
Inclusive Blocked Time % |
|
|
Inclusive Contentions |
|
|
Inclusive Contentions % |
|
|
Level |
The depth of this function in the call tree. Only in VSPerfReport command-line reports. |
|
Function Line Number |
The line number of the start of this function in the source file. |
|
Module Name |
The name of the module that contains the function. |
|
Module Path |
The path of the module that contains the function. |
|
Process ID |
The process ID (PID) of the process in which the function was executing. |
|
Process Name |
The name of the process. |
|
Source File |
The source file that contains the definition for this function. |