Modules View - sampling data
Applies to: 
Visual Studio 
Visual Studio for Mac
Note
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
The Modules view of sampling data displays performance data that is grouped by the modules that were sampled in the profiling data. Each module is the root of a hierarchical tree. The sampled functions of the module are listed underneath the module node.
Note
Enhanced security features in Windows 8 and Windows Server 2012 required significant changes in the way the Visual Studio profiler collects data on these platforms. UWP apps also require new collection techniques. See Performance Tools on Windows 8 and Windows Server 2012 applications.
If the function was executing when samples were collected (that is, the function was at the top of the call stack), the source lines and instruction addresses that were executing are listed underneath the function node. Because data is collected for a source line or an instruction pointer when the line or instruction is executing, inclusive and exclusive values are always the same for both line data and instruction data.
| Column | Description |
|---|---|
| Name | The name of the module, function, line number, or instruction pointer address. |
| Process ID | The process ID (PID) of the profiling run. |
| Process Name | The name of the process. |
| Module Name | The name of the module that contains the function, line, or instruction pointer. |
| Module Path | The path of the module that contains the module, function, line, or instruction pointer. |
| Source File | The source file that contains the definition for this function. |
| Function Line Number | The line number of the start of this function in the source file. |
| Inclusive Samples | - For a function, the number of samples in which this function or a function that was called by this function was executing; that is, the number of call stack samples that contained this function. - For a module, the number of samples in which at least one function from the module was executing. - For a line or instruction, the number of samples in which this line or instruction was executing. |
| Inclusive Samples % | - For a function or module, the percentage of all samples in the profiling run that were inclusive samples of this function or module. - For a line or instruction, the percentage of all samples in the profiling run in which this line or instruction was executing. |
| Exclusive Samples | - For a function, the number of call stack samples in which this function was directly executing; that is, the number of samples in which this function was at the top of the call stack. - For a module, the sum of exclusive samples of the functions in the module. - For a line or instruction, the number of samples in which this line or instruction was executing. |
| Exclusive Samples % | - For a function or module, the percentage of all samples in the profiling run that were exclusive samples of this function or module. - For a line or instruction, the percentage of all samples in the profiling run in which this line or instruction was executing. |