[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775?page=all ]
Steve Ebersole updated HHH-1775:
--------------------------------
Fix Version: 3.2.2
(was: 3.2.1)
not going to do this for 3.2.1
collection batch fetching
-------------------------
Key: HHH-1775
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775
Project: Hibernate3
Type: Improvement
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Priority: Minor
Fix For: 3.2.2
I have code local on my box to support "peeking" into the second level cache
when determining whether to add a particular entity/collection key to a batch load
request. If the given key is contained in the second level cache, then do not batch fetch
the entity/collection as it will be initialized from second level cache on access.
However, there are still large inefficiencies when performing this for collections; the
biggest of which currently is the fact that we retreive a IdentityMap.entrySet for each
and ever call to determine a collectiomn fetch batch. For performance reasons, we should
align this with how entity batches are handled where the entity keys considered to be
"batch loadable" are tracked seperately on the BatchFetchQueue.
--
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