Just run NH Prof through a stress test to see how well it handles scenarios where you just throw data at it.
I run into a few interesting bugs (mostly related to threading), which were luckily simple enough to handle.
The end result was:
Which is pretty impressive, I think. Just to give you an idea, we used to test NH Prof against the NHibernate integration test suite, which isn’t even half of what I threw at it now.
There is a small problem, however, the profiled application is capable of outputting data faster than NH Prof can process it. That means that unless there are some rest periods, NH Prof is in somewhat of a problem here, because it will never catch up.
I’ll post some more about how we can solve this.