Welcome to the CLR and Framework Perf Blog!


This blog will contain interesting tips and tidbits on all things CLR and the .NET Framework Perf related. It will include posts on how to improve performance from an developer perspective, provide how tos and tutorials on a bunch of perf related stuff, provide tips of debugging perf related problems and solicit feedback from our customers. Briefly --- anything perf related.

Don’t know what CLR is? It is an acronym for Common Language Runtime. 
Think of the CLR as the backbone of the .NET framework (just like everything under the hood is the backbone for your car). It is the stuff that takes the compiled program and translates it into assembly and executes it (pressing your accelerator, for example, results in higher revs, how?). It also provides all sorts of support and services for your program like memory management and exception handling to name just two (How does the car display your speed? Your mileage? Keep it in cruise?). Essentially the CLR does all the major chunks and all the bits and pieces to keep your program running smoothly (I do not have to put an analogy here, do I?).

Whenever you write your code in any managed language, e.g., C#, VB, VC++, you name it, you are using the CLR. (Try using your hands on the accelerator, it will work as long as the accelerator is pressed). The CLR cares about the common intermediate language (CIL) that is generated by compiling code in the above languages and gets them to execute on many systems.

Now, for the customary introductions. My name is Subramanian Ramaswamy (Mani) and I am a Program Manager with the CLR perf team. I will try to ensure that the blog updates atleast once monthly; if this blog is not updated, I am the guy you can holler at. Many of the blog posts you are likely to see will be from individual members from the CLR perf team.
This blog is targeted to software engineers who care about the performance of their managed code as it relates to the runtime which is executing it. Better knowledge of the runtime results in exploiting it better for faster code.
The CLR Perf team is focused on improving the performance of the runtime and a lot of talented people are working towards that. Feel free to put in the comments field topics on which you would like to see us post. You can tell us where we can improve things as we strive to improve your experience.