http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I've put the NHibernate.Initialize() call in a #if block. Personally I don't care that while profiling Nhibernate the application is slower than usual. When I'm done profiling I simply remove the conditional symbol "DEBUG_NHIBERNATE". Let me put it this way. If after each NHibernare profiling session, a slow application is the only thing that takes time, I'm very, very, very happy. But mostly I have to remind developers that certain habbits don't do well when it's come to performance. A faster profiling session would I consider as a bonus, not as a must. http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment4http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment4Mon, 16 Feb 2009 08:22:19 GMTI have identified the same problems in one of my legacy apps. When NHProf was active the application was REALLY slow! I have not mesured the difference but out of my feeling I would say at least a factor of 3 to 5 slower than without NHProf. Please note: it is a legacy app and has many "sub-optimal" queries (n+1 and the like). I'll give the new version a try as soon as possible! I still think that NHProf ROCKS!!! http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment3http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment3Sun, 15 Feb 2009 08:51:55 GMTKyle, The problem is how do you identify the key :-) http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment2http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment2Sat, 14 Feb 2009 14:51:18 GMTThat's pretty awesome. I love stories of good optimization, because I used to be in charge of profiling and identifying bottlenecks at a previous company. It was incredibly fun, and they had incredibly high restrictions on how fast things had to be and so forth. Hm, I thought I'd written a post at my blog about the two main ways of optimizing, but I can't seem to find it. Oh well. Probably most of the people who read your blog are familiar with them anyway! By the way, would it be possible to cache the StackTrace object? I am not sure what you'd use for the key, but it seems like if you were getting calls to the GetStackTrace in the same exact positions, it's gonna have the same or very similar StackTrace objects every time. Just a thought, and maybe not a good one! http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment1http://ayende.com/3872/nh-prof-performance-implications-for-the-profiled-application#comment1Sat, 14 Feb 2009 14:43:37 GMT