[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326?page=c... ] Alex Snaps commented on HHH-5326: --------------------------------- Ehcache comes with some tooling around fine tuning your cache (especially distributed). We provide a couple of panels (Hibernate & Ehcache specific ones). Currently the Hibernate one does not provide the information on that region, as indeed not maintained by Hibernate. Now I think, in order to help users understand what's going on with their caches, this information would be useful to any 2nd level cache user. I totally realize that this region is already pretty "hot" and that maintaining stats does come at prize (though much less given the j.u.c. enhancements). Maybe these could be turned on or off separately? Have a different default depending on the StatisticsImpl. ? QueryCache is definitively a double edged sword, I think providing the most accurate feedback to users would be beneficial, wdyt ? If you guys agree on the added value, I'd totally be willing to provide a patch... -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326?page=c... ] Steve Ebersole commented on HHH-5326: ------------------------------------- Note, I am not trying to say it is or it is not useful. Just trying to understand how you see it as useful. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326?page=c... ] Alex Snaps updated HHH-5326: ---------------------------- Attachment: HHH-5326.patch Here's a patch to solve that issue... The concurrent impl. sort of isn't really useful (in terms of throughput) as org.hibernate.cache.UpdateTimestampsCache methods remain all synchronized. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5326?page=c... ] Strong Liu reassigned HHH-5326: ------------------------------- Assignee: Strong Liu -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira