.Net anomalies

The .Net collector allows to insert the following types of anomalies in an Anomalies Profile:

Exceptions thrown /sec

This counter displays the number of exceptions thrown per second. These include both .NET exceptions and unmanaged exceptions that get converted into .NET exceptions e.g. null pointer reference exception in unmanaged code would get re-thrown in managed code as a .NET System.NullReferenceException; this counter includes both handled and unhandled exceptions. Exceptions should only occur in rare situations and not in the normal control flow of the program; this counter was designed as an indicator of potential performance problems due to large (>100s) rate of exceptions thrown.
The default anomaly conditions are:

Severity 1: > 0.

Raise Time: 20 seconds.

MBytes in loader heap

This counter displays the current size (in MBytes) of the memory committed by the class loader across all AppDomains. (Committed memory is the physical memory for which space has been reserved on the disk paging file.)</p>
This counter has to be in a steady state, else large fluctuations in this counter indicates there are too many assemblies loaded per AppDomain.
The default anomaly conditions are:

Severity 1: 10% far from mean
Severity 2: 20% far from mean
Severity 3: 30% far from mean

Induced Garbage Collections /sec

The number of errors per second, including connection errors, compile errors, and run-time errors. If this number is greater than 0, something is wrong with the test scripts, server configuration, or scripts in ASP pages. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 10
Severity 3: > 50

Raise Time: 60 seconds.

% Time in Garbage Collections

This indicates the percentage of time spent performing the last GC. Lower the value in the range of 5-10% is an acceptable value. There can be spikes at this counter but those are acceptable. There is a temporary suspension of all the threads during this activity. Hence there is a performance overhead we incur. Allocating large strings to cache, heavy string operations etc leave a lot of memory spaces that the GC has to clean up. Avoid such operations.
The default anomaly conditions are:

Severity 1: > 15
Severity 2: > 30
Severity 3: > 50

Raise Time: 60 seconds.

% Gen 1 / Gen 0 Collections

ratio of the number of times the generation 1 objects are garbage-collected to the number of times the generation 0 objects are garbage-collected.

100 * (Gen 1 Collections / Gen 0 Collections)

Severity 1: > 10

Raise Time: 60 seconds.

% Gen 2 / Gen 0 Collections

ratio of the number of times the generation 2 objects are garbage-collected to the number of times the generation 0 objects are garbage-collected.

100 * (Gen 2 Collections / Gen 0 Collections)

Severity 1: > 10

Raise Time: 60 seconds.





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap