[ http://216.121.112.228/browse/NH-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2125.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0Beta2
> Solution for NH2123 - Subselect in combination with a disjuction query causes an enormous memory cons
> -----------------------------------------------------------------------------------------------------
>
> Key: NH-2125
> URL: http://216.121.112.228/browse/NH-2125
> Project: NHibernate
> Issue Type: Patch
> Components: Core
> Affects Versions: 2.1.2.GA
> Reporter: martijn evens
> Priority: Minor
> Fix For: 3.2.0Beta2
>
> Attachments: NH2123.patch
>
>
> Setup:
> Simple Parent object linked to a simple Child object. The Child object is lazy loaded via subselect.
> When running a criteria query with a large disjunction (2000 params) on the parent object, which returns about 4000 objects, around 550Meg of memory is consumed. Just running the query causes this memory consumption, the child objects are not even touched or lazy loaded. I made a comparison with version 2.0.1 where only 40 Meg is consumed.
> Fix:
> In Revision 3481, the method CreateSubselects in file Nhibernate\Loader\Loader.cs was changed. Instead of using pre-created subselect statements a new subselect statement is created every time resulting in the described behavior.
> Moving back to using pre-created subselect statements, but leaving the rest of the code intact solved the issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
