4 minutes was not enough to understand that something should be studied more deeper ?

More than 6 alerts per entity? Amazing...

I believe this qualifies as "studying deeper"

A picture is worth a thousand words...

..and you seem too selfish, which is more that a thousand words indeed.

isn't Select N+1 when you select entity after entity, each in its own query?

Then how can you have 890 select N+1s with only 501 entities loaded?

Also, why would there be a large number of individual writes for a select?

Maybe it's because I don't know NH or NHProf, but I don't think I understand this picture fully.

@configurator:

Select n+1 means you're executing the same select statement several times in a session, selects that probably return the same entities. So nothing wrong with the screenshot. Also in the same session he is doing some updates.

This is exactly what my experience was with using NHProf, although less severe. Usually it's not hard to figure out what's happening (or at least get a gut feeling), but with NHProf it's so easy to spot the errors! I was hesitant at first, but when the possibility to use it for Java Hibernate seemed to be possible I was sold ;-)

One step forward, two back.. (i.e. One db call, for every 2 alerts) something wrong with this picture. (1735/3534)