[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326?page=c...
]
Alex Snaps commented on HHH-5326:
---------------------------------
Well, actually that would be the exact interest to cache tuning users (where misses would
probably be less important). Given the nature of this cache, contention might be pretty
high (like when having to support many concurrent write operations). So that seeing many
puts occurring (especially when correlating these over time), can be a hint on where the
latency goes. Not only for distributed caches, but it would probably be really important
in clustered environments.
Now from a tooling perspective, being able to track all stats and how they are influenced
at runtime by live changes to the cache configurations is obviously a plus to users in my
opinion...
UpdateTimestampsCache should maintain the statistics for its region
-------------------------------------------------------------------
Key: HHH-5326
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326
Project: Hibernate Core
Issue Type: Improvement
Components: core
Reporter: Alex Snaps
Don't know if it is by design, but the SecondLevelCacheStatistics' for the
UpdateTimestampsCache region are not maintained. Any idea why ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira