Infinispan Cache Metrics: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 38: Line 38:
</blockquote>
</blockquote>


=Resetting Statistics=
it is possible to reset statistics for an individual cache using the <tt>:reset-statistics</tt> CLI operation, applied to the management model node corresponding to that cache.





Revision as of 15:41, 26 October 2016

Internal

Overview

Each Infinispan individual cache exposes a number of performance metrics, and the cache container managing those caches aggregate some of those metrics at container level. These metrics are described below.

Average Read, Write and Remove Time

These metrics represent an individual cache read/write/remove operation average time response time, in milliseconds. For reads, the value includes hits and misses. May return null if the cache is not started. Maintained as a long. The metric always maintains the last value, even after the cache become idle. In order to reset it, you must reset underlying caches statistics, individually, with :reset-statistics.

Reference:

JDG 6 JMX JDG 6 CLI
JDG 7 JMX JDG 7 CLI

The values for these metrics are aggregated at container level, for all caches managed by this container. They are calculated by averaging values for of the corresponding values for individual cache managed by this container.

Reference:

JDG 6 JMX JDG 6 CLI
JDG 7 JMX JDG 7 CLI

Number of Entries

Cache Number of Entries

Resetting Statistics

it is possible to reset statistics for an individual cache using the :reset-statistics CLI operation, applied to the management model node corresponding to that cache.






The Cache Container

The metric at cache container level represent an aggregation of the metrics for the underlying cache and in general, are a good indicator of the activity on that specific cache node - normally, there's just one cache container.

Interesting metrics are:

  • the number of hits, misses and stores at the cache container level (JDG 7 JMX hits, misses, stores). This is an aggregation of the corresponding values for the underlying caches. It is preferable to expose these metrics as a rate per second. Some monitoring solutions allow the rate to be calculated automatically (see Data Dog counters).

Individual Caches

TODO.


JDG 7

aliases

The list of aliases for this cache container. Type: String array.

hits

The number of cache attribute hits. Type: Long. TODO c34rsz. This is an additive value for all caches managed by this container.

misses

The number of cache attribute misses. Type: Long. TODO c34rsz. This is an additive value for all caches managed by this container.

stores

The number of cache attribute put operations (writes). Type: Long. TODO c34rsz. This is an additive value for all caches managed by this container.


JDG 6

cluster-members

See JMX clusterMembers.

created-cache-count

See JMX createdCacheCount.