2015-07-06 16:05 GMT+01:00 Greg Young <[email protected]>: > "If the processor and memory load is minimal, what do you suppose the > system is doing the rest of the time? If the system has reached it's > maximum capacity, at least one of the basic resources (CPU, memory, > disk IO, network IO) should be near it's maximum capacity. Since you > can run the same application twice in parallel and get twice the > throughput, it would seem this is not a matter of resource exhaustion, > and so I wouldn't expect any significant gains from any typical > algorithmic optimizations." > > My guess is the time is being spent blocking on N+1 as an example. > This would explain the low load + performance problems > >
Yes that's a possibility. Should show as high disk IO waiting times (or high CPU load if the interesting data has been cached. SQL Profiler would also be a way to check for that. My memory of NH 1.2 is foggy - later versions have more features to avoid N+1, but this is probably more an issue with how the program is implemented rather than NHibernate version. /Oskar -- 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.
