Hello- It seems that nHibernate 3.1 performance around an EAV schema is very poor. Dealing with 4000 primary objects with 60 different attribute types: a total of 140,000 object-attribute rows in the database. So, to fully hydrate the 4000 primary objects, there are multiple sets of 140,000 calls being made in .NET to initialize and populate the collections of attributes. This process takes 20+ seconds, which is wholly unnacceptable for a 4000 item resultset. Join and Eager fetch plans do not help. It is not an N+1 issue as far as I can tell -- only 3 queries are being made against the DB.
I posted this here the other day, but have not been able to find a solution; is there no feasible solution with nHibernate, or any ORM for that matter? http://stackoverflow.com/questions/5682668/how-to-resolve-poor-nhibernate-collection-initialization/ Thanks for any help, I'd rather not have to throw nHibernate out here- ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera -- 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.
