eG Help

In Apache Ignite architecture, a cache layer sits between in-memory database and node processor, it is the place where most used objects are stored in key-value pairs. Cache entry processor is responsible for creating and managing the cache and ensuring that caches operations are robust and atomic. The Cache entry processor is responsible for providing the user with an existing instance of cache to write, creating the cache dynamically, destroying the caches which are no longer required and ensuring the atomicity of caching operations.

Since caching is an important function for applications which provide real time interaction for users, it is necessary for cache to work properly and is able to serve the data most of the times. That's the reason it important to ensure that cache processor is working as expected and needs to be fixed immediately if there is an issue.

This test monitors the Entry Cache Processor to analyze the health of cache processor and provides key insights to administrators to understand the health of Cache Entry Processor.

Measurement	Description	Measurement Unit	Interpretation
heapEntriesCount	Indicates the total number of entries in heap memory which represent all instances of cache.	Number	If the number is high, administrators might have to think about clearing the cache or adding more memory to cache.
ePAvgInvocationTime	Indicates the mean time to execute cache invokes. This is the processor time rather then the time to serve data from cache.	Seconds	A high value indicates that either processor is too busy serving high number of requests or cache is not working as expected.
ePHits	Indicates the total number of invocation on keys which exist in the cache.	Number	A high number is desirable and means that cache is working as expected.
ePHitPercentage	Indicates the percentage of invocation on keys which exist in the cache.	Percentage	A high percentage value is desirable and indicates proper functioning of cache processor.
ePInvocations	Indicates the total number of invocations of cache through cache processor	Number	A very high number of invocations might just overload the cache processor and will delay the cache response. This number needs to be managed optimally.
ePMisses	Indicates the total number of invocation on keys which don't exist in the cache.	Number	Very low number indicates that either cache is not functioning properly or for some reason the data requests are completely new. Administrators may need to analyze further in this case.
ePMissPercentage	Indicates the percentage of invocation on keys which don't exist in the cache.	Percentage	Very low number indicates that either cache is not functioning properly or for some reason the data requests are completely new. Administrators may need to analyze further in this case.
ePPuts	Indicates the total number of cache invocations which caused an update in cache.	Number	Very high number of updates in the cache over a very short period of time means cache is not in sync with database or has not been refreshed for long time.
ePReadOnlyInvocations	Indicates the total number of cache invocations which caused no update in cache.	Number	A high number is desirable and means that cache is working as expected.
ePRemovals	Indicates the total number of cache invocations which caused a removal.	Number	Very high number of removals in the cache over a very short period of time means cache is not in sync with database or has not been refreshed for long time.