http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I used the profiler and its pretty neat. One thing I found troubling is the N + 1 problem. I was expecting the profiler to "highlight" the code that is doing this and suggest (may be) a way to avoid this thing. Not only a stack trace. If it could show the Query source not just the "Sql" version ... that would really shed some light . Cause I'm eagerly fetching the required data, still a lazy loading of the same data is triggered from somewhere which calls the database for N + 1 times (for same record). What I would like to see in the profiler, in addition to the sql query, the source query or entity which "caused" this query to go to the database with a hint to do a better thing ... I hope this is not hard to implement ... http://ayende.com/4780/nhibernate-profiler-update-client-profile-nhibernate-3-x-updates#comment2http://ayende.com/4780/nhibernate-profiler-update-client-profile-nhibernate-3-x-updates#comment2Tue, 22 Mar 2011 10:00:51 GMTThis update ist pretty awesome and helps me a lot! Thank you! http://ayende.com/4780/nhibernate-profiler-update-client-profile-nhibernate-3-x-updates#comment1http://ayende.com/4780/nhibernate-profiler-update-client-profile-nhibernate-3-x-updates#comment1Sun, 13 Mar 2011 18:30:45 GMT