Is there a hard requirement to fully hydrate the 4000 primary objects at startup, or is this just the way it happens to be implemented now?
If it's NOT a hard requirement, turning on lazy loading might be an option. This has significantly improved startup performance in my application, at least. The downside of lazy loading is that session management can be quite a bit more complicated, depending on the situation. -Tom Bushell -- 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.
