On Friday, October 10, 2014 7:33:57 AM UTC+3, Darren Kopp wrote: > > I would guess that the performance you see on your machine is the same as > on Azure, but you're likely hitting your cpu limits. I'm not sure ordering > would have any issue on hydration, unless perhaps you have a poor hash code > algorithm and perhaps were hitting worst case scenarios on hash tables, but > that also seems pretty suspect. Do you have any .net profiling data > comparing the two scenarios you outlined? >
I did, but I didn't save it -- and guess what, by the end of the day, the probelm disappeared by itself. The hot spots found by the profiler were all somewhere in NHibernate's proxy generation code paths, which seemed extremely weird to me. I'm not sure how to interpret your comment on CPU limits. Maybe I wasn't very clear in my original post: running the query on the same computer (my dev machine) produced wildly different results with the same code, depending on which database I was hitting -- even though my local database was a very recent (minutes old) copy of the production DB, so the data sets were nearly identical. And removing the OrderBy eliminated the difference. I'll get back to this issue if it reappears and I manage to gather some more diagnostic data. -Lauri -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
