Any way to get more statistics and response-time info from cache processes?

Question

I'm currently involved in an evaluation of Coherence for use as a global in-core cache/DB for data in the GB range. We'll try to run multiple cache process per cache in order to stay below 512MB heap-space per cache process.
In order to tune cache access times and understand the dynamic behaviour of the app we'd like to see some statistics info for cache access, e. g.
- requests processed per cache (process)
- requests answer time (per request, min, max, avg, median etc.)
- request answer size (number of cache entries returned, size of entries etc.)
- whatever else that helps ...
We are in position to get this kind of statistics info on the application side (when we call Coherence-APIs) but we'd need to see the statistics on a technical level per cache process.
We know about JMX/MBeans but that does not allow us to come up with log-files for statistical analysis and there is no way to correlate requests from the application to any statistics information (what request did cause what effect).
Any way to tell the cache processes to provide this kind of (logging) info (mesurements per request) and some summary.

Answer 1

David,
In addition to statistics that you can collect at the client tier (measuring the latency of individual cache calls), you could use a number of attributes exposed by the ServiceMBean.
If you look at a ServiceMBean for your partitioned cache service, the RequestAverageDuration and RequestMaxDuration attributes describe the latency of the underlying communication tier as seen from the client and does not include the serialization/deseriation cost.
The TaskAverageDuration, TaskMaxBacklog and ThreadAverageActiveCount expose the latency and expenses as seen by the server side, excluding the network tier expenses.
Also, there are number of statistics exposed by the CacheMBean related to the underlying backing map efficiency such as AverageGetMillis, AverageHitMillis, AverageMissMillis and AveragePutMillis.
You can also create your own subclasses for backing map implementation and implement custom MBeans that would expose any addition information you wish to collect.
Regards,
Gene