Infinispan Cache Metrics: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


* [[Infinispan_Monitoring#Metrics|Infinispan Monitoring]]
* [[Infinispan_Monitoring#Metrics|Infinispan Monitoring]]
* [[Infinispan_Metrics_Reference#Metrics|Infinispan Metrics Reference]]




=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=
The metrics represent the 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. It always maintains the last value, even after the underlying caches become idle. In order to reset it, you must reset underlying caches statistics, individually, with [[#Resetting_Statistics|:reset-statistics]].
The value for these metrics are aggregated at [[Infinispan_Cache_Container_Metrics#Average_Read.2C_Write_and_Remove_Time|cache container level]].
{|
| [[JDG_6_JMX#averageReadTime_individual_cache|JDG 6 JMX]] || [[JDG 6 CLI#average-read-time_individual_cache|JDG 6 CLI]]
|-
| [[JDG 7 JMX#averageReadTime_individual_cache|JDG 7 JMX]] ||  [[JDG 7 CLI#average-read-time_individual_cache|JDG 7 CLI]]
|-
|}





Revision as of 15:11, 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

The metrics represent the 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. It always maintains the last value, even after the underlying caches become idle. In order to reset it, you must reset underlying caches statistics, individually, with :reset-statistics.

The value for these metrics are aggregated at cache container level.

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








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).
  • the total number of entries at cache container level. This is an aggregation of the corresponding values for the underlying caches. For more details on the cache number of entries see Infinispan Cache Number of Entries.

Individual Caches

TODO.