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: 18 | Comments: 84

filter by tags archive

UberProf performance challenges

time to read 1 min | 169 words

One of the things that the profiler is supposed to do is to handle large amount of data, so I was pretty bummed to hear that users are running into issues when they try to use the profiler in high load scenarios, such as load tests.

Luckily, one of the things that the profiler can do is output to a file, which let me simulate what is going on on the customer site very easily.

The first performance problem is that the profiler isn’t processing things fast enough:

image

The second is that there are some things that just totally breaks my expectations

image

There are solutions for those problems, and I guess that I know what I’ll be doing in the near future :-)


Comments

Romain Verdier

Is the rhino in the waiting dialog animated?

Glenn F. Henriksen

So that's 53k queries in one data context? Seems a bit much :D

Ayende Rahien

Yes, that is NOT something that the profiler expects to see, I am afraid to say.

Glenn F. Henriksen

What's with the loading picture, 160.062 out of 11.957? Textbox overflow?

Ayende Rahien

Glenn,

160K loaded, 11K remaining to be processed.

Glenn F. Henriksen

Ah, I guess it's easier to see it when you see the numbers counting.

smurf

if you write about features of ÜberProf, do they affect all profilers or do i need an ÜberProf license to get them?

Ayende Rahien

smurf,

When I am talking about UberProf, I am referring to all profilers.

Paulo Quicoli

I dont know internals of your loading data... but, maybe, use some of parallelism from .NET 4 would be good. :)

John Farrell

Bah, thats nothing, I've done 1.6 million in a single context before. :p

Why? It was quicker to drag a table into EF than write the sql query manually for a simple nightly processing job. Performance overhead for using an ORM was in "who cares" territory so it worked.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. Buffer allocation strategies: A possible solution - 3 days from now
  2. Buffer allocation strategies: Explaining the solution - 4 days from now
  3. Buffer allocation strategies: Bad usage patterns - 5 days from now
  4. The useless text book algorithms - 6 days from now
  5. Find the bug: The concurrent memory buster - 7 days from now

There are posts all the way to Sep 11, 2015

RECENT SERIES

  1. Find the bug (5):
    20 Apr 2011 - Why do I get a Null Reference Exception?
  2. Production postmortem (10):
    03 Sep 2015 - The industry at large
  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