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,026 | Comments: 44,842

filter by tags archive

Bug HuntWhat made this blog slow?

time to read 1 min | 98 words

A while ago the blog start taking 100% CPU on the client machines. Obviously we were doing something very wrong there, but what exactly was it?

We track down the problem to the following code, can you figure out what the problem?



More posts in "Bug Hunt" series:

  1. (30 Jan 2012) What made this blog slow?
  2. (27 Jan 2012) What made this blog slow?



ajaxComplete calls fetchResults causes ajaxComplete causes fetchResults....

Josh Reuben

IIS applicationPool MaxConcurrentRequestsPerCPU ?


ajaxComplete triggers fetchResults which in turn triggers ajaxComplete

Ryan Heath

Each and every ajax call will trigger an ajaxComplete, which will trigger an ajax get, which will trigger an ajaxComplete, which will trigger an ajax get, which etc etc ... ;)

// Ryan

Frank Quednau

Kudos ayende for not misusing your position with regard of having the keenest and fastest bug finders.

PS I regularly must reload your captchas because they are hard. I am staring at what seems to be hebrew...

Matt Owen

I just happened to have Fiddler and this blog open on the day this happened. I saw the madness for myself. Hilarity ensued.

Rob White

ajaxComplete -> fetchResults -> ajaxComplete etc.

Even on a Friday, after a drink I spotted that one.

I assume that the real scenario was not as clearly presented.

More hard things please. ;-)

João Bragança

It would have worked if the profiler itself did not return X-RavenDb-Profiling-Id. Unless the profiler markup / js also needs this


I'm tempted to say stuff like "idiotic", "stupid" and "wtf?!". But I'm not going to.


I assume the fix is :-

if (!id) fetchresults(id.split(', '));

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats