Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 10 | Comments: 35

filter by tags archive

NHibernate Profiler update: Client Profile & NHibernate 3.x updates

time to read 1 min | 139 words

We just finished a pretty major change to how the NHibernate Profiler interacts with NHibernate. That change was mostly driven out of the desire to fully support running under the client profile and to allow us to support the new logging infrastructure in NHibernate 3.x.

The good news, this is done Smile, you can now use NH Prof from the client profile, and you don’t need to do anything to make it work for NHibernate 3.x.

The slightly bad news is that if you were relying on log4net conifguration to configure NH Prof, there is a breaking change that affects you. Basically, you need to update your configuration. You can find the full details on how to do this in the documentation.


Comments

Daniel Lang

This update ist pretty awesome and helps me a lot! Thank you!

jalchr

I 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 ...

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. Production postmortem: The case of the memory eater and high load - 2 days from now
  2. Production postmortem: The case of the lying configuration file - 3 days from now
  3. Production postmortem: The industry at large - 4 days from now
  4. The insidious cost of allocations - 5 days from now
  5. Find the bug: The concurrent memory buster - 6 days from now

And 4 more posts are pending...

There are posts all the way to Sep 10, 2015

RECENT SERIES

  1. Find the bug (5):
    20 Apr 2011 - Why do I get a Null Reference Exception?
  2. Production postmortem (10):
    14 Aug 2015 - The case of the man in the middle
  3. What is new in RavenDB 3.5 (7):
    12 Aug 2015 - Monitoring support
  4. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats