The metrics view shows real-time data for the profiled process(es). It contains two charts giving information about
CPU and memory usage history and a list with current values of selected .NET performance counters.
The meaning of each counter is given in the table below.
Percentage of the elapsed time that the process has used to execute code.
The amount of physical memory in use by the process.
Current memory allocated in bytes on the GC Heaps excluding Gen0. This most closely resembles the actual used GC memory.
# Gen 0 GC
Number of times the generation 0 objects have been garbage collected since the start of the application.
# Gen 1 GC
Number of times the generation 1 objects have been garbage collected since the start of the application.
# Gen 2 GC
Number of times the generation 2 objects have been garbage collected since the start of the application.
# Induced GC
Number of times a garbage collection was performed because of an explicit call to GC.Collect.
Time in GC
Percentage of the elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle.
Time in JIT
Percentage of elapsed time spent in JIT compilation since the last JIT compilation phase.
Total number of times threads in the CLR have attempted to acquire a managed lock unsuccessfully.
Current rate at which threads in the runtime attempt to acquire a managed lock unsuccessfully.
Total number of exceptions thrown since the start of the application.
Current rate at which exceptions are being thrown.
Managed Heap Total Size
Current memory allocated in bytes on the 4 GC Heaps (Gen0, Gen1, Gen2, Large objects).
If values for some of the .NET performance counters are not shown you may need to re-register
them. To do this start an administrator command prompt and execute the following commands:
- unlodctr .NETFramework
- lodctr %WINDIR%\Microsoft.NET\Framework\<Framework_ver>\CORPerfMonSymbols.ini,
where <Framework_ver> is the directory of the .NET Framework version which contains the CORPerfMonSymbols.ini file.
It should be either v4.0.xxx or v2.0.xxx if 4.0 is not installed.
There is a known limitation of JustTrace's add-in. It is unable to read performance counters of 64-bit processes.
The reason is that 32-bit processes (such as Visual Studio) cannot read the counters for 64-bit processes. If you want to monitor
them while profiling, run your 64-bit application using the standalone version of JustTrace.