[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3191) QueryPlanCache cache size
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191?page=c...
]
Julien Kirch commented on HHH-3191:
-----------------------------------
I fully agree with this, but our system use soft references in others cases where objects
are much more costly to recreate than compiled querries,
so when the JVM needs some memory I would discard other objects types than these.
If I need to tune the caches size for my special need I'll also check that my memory
consequences induced by this configuration. And if an OOME occurs because of a few
hundreds compiled querries, this means than I have a huge problem elsewhere.
In a few words: I agree with the soft-references behaviour you describe, and I would be
allowed to tune its implementation for our specific needs.
QueryPlanCache cache size
-------------------------
Key: HHH-3191
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191
Project: Hibernate3
Issue Type: Improvement
Components: query-hql
Affects Versions: 3.2.6
Environment: Hibernate 3.2.6, all platform
Reporter: Julien Kirch
On a large application with many (currently 696) named queries in hbm files we have a
performance issue with the QueryPlanCache cache size:
The SoftLimitMRUCache used in the QueryPlanCache use 128 hard references, the other being
soft references, and this number is hardcoded.
As we have much more querries in the application, we spend much time in recompiling the
same queries when they are evicted from the cache.
As the QueryPlanCache has a SessionFactoryImplementor as parameter, adding a new
parameter to define the query cache plan size would be trivial; what's your opinion
about this ?
--
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