ASP .Net CLR GC Test
This test monitors the memory allocation activity of the ASP .Net server, in terms of heaps when objects are created and managed.
Target of the test : An ASP .Net server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every worker process on the ASP .Net server.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the specified Host listens. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Heap mem usage |
The number of bytes committed by managed objects. This is the sum of the large object heap and the generation 0, 1, and 2 heaps. |
MB |
|
Gen 0 collections |
The rate at which the generation 0 objects (youngest; most recently allocated) are garbage collected (Gen 0 GC) since the start of the application. |
Collections/Sec |
|
Gen 1 collections |
The rate at which the generation 1 objects have been garbage collected since the start of the application. Objects that survive are promoted to generation 2. |
Collections/Sec |
|
Gen 2 collections |
The number of times generation 2 objects have been garbage collected since the start of the application. |
Number |
Generation 2 is the highest, thus objects that survive collection remain in generation 2. Gen 2 collections can be very expensive, especially if the size of the Gen 2 heap is huge. |
Time in gc |
% Time in GC is the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. |
Percent |
This measure is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and conserve memory. This measure is updated only at the end of every GC and the measure reflects the last observed value; its not an average. |