Certainly that’s one of the most frequently asked questions I get (at the PDC too!). So since PDC already happened I can tell the rest of you about the new stuff happened in GC in CLR 2.0. The slides can be downloaded here.
Post by this author
I will be giving a GC talk at the PDC this September. This talk is to give you a close up view of the CLR GC so I hope to see all you hard core .NET developers there!
I will talk about some internal details of generations,
In this article I’ll talk about things you want to look for when you look at the managed heap in your applications to determine if you have a healthy heap. I’ll touch on some topics related to large heaps and the implications you want to be aware of when you have an application that maintains or has potential for the need to maintain a managed heap of large sizes.
In this article I’ll talk about pinning and weak references – stuff related to GC handles.
(I was planning on talking about finalization in this part of the “Using GC Efficiently” series but since I already covered it in pretty much detail in one of my previous blog entries I won’t repeat it here.
I was writing an internal wiki page on performance and thought this info is useful to many external readers as well so here it goes.
vadump is a good start. It’s an mstools tool – meaning you can find it on your NT CD under bin\mstools.
In the WinDev conference that I just went to, there seems to be some confusion over finalization (such as why it even exists and etc) and other areas. I hope the following will clear up that confusion. If not, let me know.
In this article I’ll talk about different flavors of GC, the design goals behind each of them and how they work differently from each other so you can make a good decision of which flavor of GC you should choose for your applications.
I am going to WinDev this year to give 2 performance talks. Check out:
http://butrain.bu.edu/windev/track2.asp (it’s from Oct 25 to 29)
Below is the description:
C5 – CLR PerformanceWrite faster managed code! Learn about performance engineering, tools and issues specific to managed code including: garbage collection (GC),
So the goal here is to explain the cost of things so you can make good decisions in your managed memory usage – it’s not to explain GC itself – it’s to explain how to use it. I assume most of you are more interested in using a garbage collector than implementing one yourself.
Yep, now I have a blog too.
I work on the CLR Performance Team so naturally I will be writing about performance.