Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was reading a blog entry by Josh Smith where he used a cache mechanism in order to “reduce managed heap fragmentation”. His caching reduces the number of short-lived objects being created at the cost of slightly slower execution speed.
How much of a problem is managed heap fragmentation in a managed language like C#? How can you diagnose if it’s an issue? In what situations would you typically need to address it?
Not too quickly. It is generally very cheap to have short lived objects. For a cache to be profitable there would have to be (very) many candiadates and they should live long enough to make it to the next generation.
With a Profiler. I’m not so sure the author of the article did that.
As far as I know it is rare. .NET has a compacting Garbage collector, that prevents most forms of fragmentation. There are issues with the Large Object Heap sometimes.
Edit:
When you go through the comments below the article you will find that someone measured it and found the cache to be a lot slower than creating new eventargs each time.
Conclusion: Measure before you start optimizing. This was not a good idea/example.