The answer to your question is "no", simply because it would change from release to release, and we wouldn't want anybody to depend on it.
A few that I know: 1) Inlining is inhibited in debug mode. 2) If you look at the IL, you'll see that there are some noops inserted. They're put there so that there are instructions associated with the lines you might want to put breakpoints on. Eric -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Schmied Sent: Wednesday, February 08, 2006 11:14 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] .NET micro-benchmarking > 2) You will get very little useful information about performance > optimization running without JIT optimizations, because the debug case > is optimized for debugging. In other words, it's deliberately slowed > down to make debugging easier. Some things might be slowed down by > 10%, some by 100%, and some not at all. Hm, that's interesting to know. Deliberately slowed down to make debugging easier. Is there concrete information on this slow-down in the debug case available online? > Bonus comment: > > Premature optimization is one of the two greatest programming sins > (the other being premature generalization). Yeah, yeah. Again, I don't do this in order to "optimize" my applications or something. I want to get an impression of the performance of a few low-level code fragments. I won't base any application design on the results, I promise :) Fabian =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
