Ayende @ Rahien

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


+972 52-548-6969

, @ Q c

Posts: 6,128 | Comments: 45,546

filter by tags archive

Poor man’s guide to database optimization - by the Marquis de Sade

time to read 2 min | 321 words

One of the more common problems that I see over and over again in many applications is that test databases are too fast. As I have shown, this can easily lead to really sever cases of chattiness with the database, and all while the developer is totally oblivious.

This is especially true when you develop against a local database with almost no data, and deploy to a network database with lots of data. SELECT N+1 is bad enough, but when N is in the hundreds or more, it gets bad. The main problem is that developers aren’t really aware of that. This don’t see the problem, or feel it. And while they could fix it if they caught it in time, trying to come back to an existing application and fix all the many places where they assumed database access is free is a daunting task.

Therefore, I have set out to solve the problem. Obviously it is a problem with the developers not paying attention, but how can we deal with that?

Well, you could buy the NHibernate Profiler, which is my official recommendation. Or, if you don’t feel like spending money on this, you can utilize the following interceptor. That will make the developers sit up and notice when they start talking to the database.

public class SlowDownDudeInterceptor : EmptyInterceptor
    public override SqlString OnPrepareStatement(SqlString sql)
        return sql.Insert(0, "waitfor delay '0:0:0.5'" + Environment.NewLine);

Don’t go to production with this!


Markus Zywitza

Just an idea: Wouldn't such a thing be a good idea to simulate load on the DB server?


I always thought that each db call should make the workstation beep, or make a systray thingee blink. I never got around to implementing anything like that, though.


I always output (and inspect) queries into the console/debug stream for database tests. It's fairly easy to do with any ORM that implements a unit-of-work pattern and with log4net.

Chris Missal

This is a really good idea, but why stop there, maybe we can speed it up by using:

"waitfor delay '-0:0:0.5'"

What do you think?? ;)



Could you give a quick example of how you would do that with say NHibernate? Thanks



NHibernate is by far the easiest ORM to implement logging. For unit testing you just add the configuration property true into the Web.Config/App.config file.

If you want to configure log4net to log into event log, DB, etc, here is the link: nhforge.org/.../...et-for-use-with-nhibernate.aspx

Entity Framework was a different story. It required a provider wrapper that sits between the object context and the database provider.

Comment preview

Comments have been closed on this topic.


  1. The low level interview question - 11 hours from now
  2. The worker pattern - 3 days from now

There are posts all the way to May 30, 2016


  1. The design of RavenDB 4.0 (14):
    26 May 2016 - The client side
  2. RavenDB 3.5 whirl wind tour (14):
    25 May 2016 - Got anything to declare, ya smuggler?
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series



Main feed Feed Stats
Comments feed   Comments Feed Stats