Performance Rules by ID

DA0002: VSPerfCorProf.dll is missing

The profiler could not find VSPerfCorProf.dll during the profiling run. This warning occurs when command-line tools for the collection of profiler data are used without using the VSPerfCLREnv.cmd tool to initialize the necessary environment variables.

DA0004: High processor usage

Processor (CPU) utilization was significantly high in profiling data that was collected using the instrumentation method. Consider using the sampling profiling method when profiling a CPU bound application.

DA0006: Override Equals() for value types

Calls to the Equals method or the equality operators of a public value type are a significant proportion of the profiling data. Consider implementing a more efficient method.

DA0008: Few samples collected

Only a few samples were collected in the profiling run. Consider a longer run or faster sampling rate for more significant results.

DA0010: Expensive GetHashCode

Calls to the GetHashCode method of the type are a significant proportion of the profiling data or the method allocates memory.

DA0012: Significant amount of Reflection

Calls to the System.Reflection methods such as InvokeMember and GetMember or to Type methods such as MemberInvoke are a significant proportion of the profiling data. When you can, consider replacing these methods with early binding to the methods of dependent assemblies.

DA0014: Extremely high rates of paging active memory to disk

System performance data that was collected in the profiling run indicates that an extremely high rate of paging active memory to and from the disk occurred throughout the profiling run. Paging rates at this level usually will impact application performance and responsiveness. Consider reducing memory allocations by revising algorithms. You might also have to consider the memory requirements of your application. running profiling again on a computer that has more memory.

DA0018: 32-bit Application running at process managed memory limits

System data that was collected during the profiling run indicates the .NET Framework memory heaps approached the maximum size the managed heaps can grow to in a 32-bit process. The value reported is the maximum observed value of the heaps while the profiled process being was active. Consider optimizing the use of managed resources by the application.

DA0022: High rate of Gen 2 garbage collections

System performance data that was collected during profiling indicate that a significant proportion of the memory for.NET Framework objects was reclaimed in generation 2 of garbage collection compared to generation 0 and generation 1 garbage collections.

DA0024: Excessive GC CPU Time

System performance data that was collected during profiling indicates that the amount of time spent in garbage collection is excessively high compared with the total application processing time.

DA0029: Unsupported CLR Version

You are trying to profile an application that uses the .NET Framework version 1.1 that is not supported by the Profiling Tools.

DA0038: High Rate of Lock contentions

System performance data that is collected with the profiling data indicates that a significantly high rate of lock contentions occurred during application execution. Consider profiling again using the concurrency profiling method to find the cause of the contentions.

DA0501: Average CPU consumption by the Process being profiled.

This message reports the percentage of time that a processor was busy executing instructions from the application. The reported value is the average over all the measurement intervals in which the process being profiled was active. The value of value can be greater than 100% on a machine with more than one processor.

DA0503: Average Working Set in Bytes for the Process being profiled

This message reports the average amount of physical memory that the process is currently using in bytes (the working set). The process working set represents pages from the process address space that currently reside in physical memory.

DA0505: Average Private Bytes allocated for the Process being profiled

This message reports the average amount of virtual memory that the process has currently allocated in bytes (Private bytes). Private bytes represents virtual memory locations that were allocated by the process that can only be accessed by threads running inside the process.