Hi,
I ran into deep performance trouble!
I have many to one relations were I defined inverse collections. These
look like this:
In my Parent class I have an Property "Child"
<many-to-one name="Child" cascade="none">
<column name="Column1" />
<column name="Column2" />
<column name="Column3" />
</many-to-one>
In my Child class I have a Property IList<Parent> FkCollection
<bag name="FkCollection" inverse="true" lazy="true" cascade="all">
<key>
<column name="Column1" />
<column name="Column2" />
<column name="Column3" />
</key>
<one-to-many class="ChildClass,Assembly" />
</bag>
The Performance is a desaster! I did some research that bag is indeed
a performance killer, but recommanded for inverse collections.
1. Do I gain anything by changing it to lists or another collection-
type
2. What kind of changes would be needed? (e.g. how would the index and
other performance-critical settings look like in my case?)
3. does lazy setting influence the performance in my case
4. I have the chance to reduce the key to only two values instead of
three - is it worth to make the changes
5. As Type of my collection attribute is there a chance to use List<T>
instead of IList<T> with another collection type like <list>
Thank you so much for your support
antoschka
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
