Optimizing managed C# vs. native C++ code
Raymond Chen (aka "fixed more Windows bugs than you've had hot dinners") and Rico Mariani (aka "Mr .NET Performance") have been running a great series of articles where they write and then optimize the same application in two different languages: native C++ and managed C#. The easiest starting point for the two sets of articles is "Performance Quiz #6 -- Chinese/English Dictionary reader".
There's a lot of good information in both the articles and the reader comments, and if you've got the time they're well worth studying for hints on how to write and benchmark high-performance code. The summary is a compelling argument for .NET:
- A line-for-line translation of the original C++ code into C# ran 10 times faster than the C++ code.
- It took five different optimizations (one of which introduced a bug) for the C++ code to match the speed of the unaltered C# code.
- After Raymond's sixth optimization, his C++ code finally beat the C# code — because the runtime got down to where the 60ms startup overhead of the CLR made a difference!
- To accomplish this, Raymond had to:
- Write his own file/io stuff
- Write his own string class
- Write his own allocator
- Write his own international mapping
So yes, C++ code can be faster than C# code — but when you look at all the work Raymond had to go through to achieve that, you have to ask yourself "is it worth it?"
Edit: Jeff Atwood has posted a graph illustrating the diminishing returns of Raymond's optimization efforts.