...
By default all server statistics tracers are disabled as trace logging is not zero garbage and introduces cpu overhead in computing statistics. While tracing heartbeats isn't recommended in production, enabling server statistics trace output can be useful for debugging and performance tuning. To enable you will need to configure the appropriate tracers at the debug level. See the Heartbeat Trace Output Trace Loggers section for more detail.
| Code Block | ||
|---|---|---|
| ||
<xvms>
<xvmname="my-xvm">
<heartbeats enabled="true" interval="5">
<logging enabled="true"></logging>
<tracing enabled="true"></tracing>
</heartbeats>
</xvm>
</xvms> |
...
- A miss has been recorded for the pool in a given interval and it results in a new object being allocated.
- The number of preallocated obects taken from a pool drops below the configured value for the pool depletion threshold.
Sample Trace Output
| div | ||
|---|---|---|
| ||
|
| Stat | Description |
|---|---|
PUT | The overall number of times items were put (returned) to a pool. |
DPUT | The number of times items were put (returned) to a pool since the last time the pool was reported in a heartbeat (the delta). |
GET | The overall number of times an item was taken from a pool.
|
| DGET | The number of times an item was taken from a pool since the last time the pool was reported in a heartbeat (the delta). |
| HIT | The overall number of times that an item taken from a pool was satisfied by there being an available item in the pool. |
| DHIT | The number of times that an item taken from a pool was satisfied by there being an available item in the pool since the last time the pool was reported in a heartbeat(the delta). |
| MISS | The overall number of times that an item taken from a pool was not satisfied by there being an available item in the pool resulting in an allocation. |
| DMISS | The number of times that an item taken from a pool was not satisfied by there being an available item in the pool resulting in an allocation since the last time the pool was reported in a heartbeat. |
| GROW | The overall number of times the capacity of a pool had to be increased to accomodate returned items. |
| DGROW | The number of times the capacity of a pool had to be increased to accomodate returned items since the last time the pool was reported in a heartbeat. |
EVIC | The overall number of items that were evicted from the pool because the pool did not have an adequate capactiy to store them. |
| DEVIC | The overall number of items that were evicted from the pool because the pool did not have an adequate capactiy to store them since the last time the pool was reported in a heartbeat. |
| DWSH | The overall number of times that an item return to the pool was washed (e.g. fields reset) in the detached pool washer thread. |
| DDWSH | The number of times that an item return to the pool was washed (e.g. fields reset) in the detached pool washer thread since the last time the pool was reported in a heartbeat |
| SIZE | The number of items that are currently in the pool available for pool gets. This number will be 0 if all objects that have been allocated by the pool have been taken.
|
| PRE | The number of items initially preallocated for the pool. |
| CAP | The capacity of the backing array that is allocated to hold available pool items that have been preallocated or returned to the pool.
|
| NAME | The unique identifier for the pool. |
If pool items are not being leaked, GET - PUT indicates the number of items that have been taken from the pool and not returned ... e.g. items that are being held by messages in the transaction processing pipeline or application state.Engine Stats
Stats collected by the AEP engine underlying your application are also included in heartbeats. Tracing of engine stats can be enabled with the following.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<xvms>
<xvm name="my-xvm">
<heartbeats enabled="true" interval="5">
<tracing enabled="true">
<traceAppStats>true</traceAppStats>
</tracing>
</heartbeats>
</xvm>
</xvms> |
See AEP Engine Statistics for more detail about engine stats.
User Stats
User stats collected by your application are also included in heartbeats. Tracing of user stats can be enabled with the following.
...
- User Defined App Stats for adding stats specific to your application to heartbeats.
Engine Stats
Stats collected by the AEP engine underlying your application are also included in heartbeats. Tracing of engine stats can be enabled with the following.
...
<xvms>
<xvm name="my-xvm">
<heartbeats enabled="true" interval="5">
<tracing enabled="true">
<traceAppStats>true</traceAppStats>
</tracing>
</heartbeats>
</xvm>
</xvms>See AEP Engine Statistics for more detail about engine stats.