| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Heap_used |
The liveCache memory that is been used currently |
MB
|
The memory requirements in the OMS heap are very high for the running DB procedures. If the memory utilization in the OMS heap reaches 100% of its limit, there is the risk of errors in the DB procedures (Out of Memory Exceptions), or that OMS version data is swapped from the OMS heap to the global data cache (OMS version is unloaded). It is recommended that you configure the general database parameter CACHE_SIZE and the liveCache parameter OMS_HEAP_LIMIT in such a way that it prevents swapping at the operating system level and errors in DB procedures.
|
| Reserved_size |
The memory managed by the allocator |
MB
|
|
| Memory_allocation_rate |
The number of memory allocations per second |
Allocations/Sec
|
A higher rate indicates higher and faster memory utilization.
|
| Memory_release_rate |
The number of memory releases per second |
Releases/Sec
|
|
| Spinlock_rate |
When a requested lock is not available, then the process will spin and try again to acquire the lock. This is known as a Spinlock. This measure indicates the number of attempts that were made per second to acquire a spinlock. |
Attempts/Sec
|
A consistent increase in this rate indicates that some locks have been held for too long a time.
|
| Collision_rate |
The rate at which attempts to get a spinlock failed |
Collisions/Sec
|
|
| Spinloop_rate |
The rate at which attempts were made to acquire a spinlock without prior release of the CPU |
Attempts/Sec
|
|
| Yieldloop_rate |
The rate at which attempts were made to acquire a spinlock after prior release of the CPU |
Attempts/Sec
|
|
| Errors_rate |
The rate at which errors were detected and automatically corrected |
Errors/Sec
|
|