Re:On Stack Overflow's recent battles with the .NET Garbage ...
by ableal on Friday October 28, 2011 @05:41AM
(#3167601)
These two phrases, early in the article, could give someone an interesting problem to solve:
Our initial tag engine design was a GC nightmare. The worst possible type memory allocation. Lots of objects with lots of references that lived just enough time to get into generation 2 (which was collected every couple of minutes on our web servers).
Interestingly, the worst possible scenario for the GC is quite common in our environment. We quite often cache information for 1 to 5 minutes.
(Curiously, this is under a header mentioning "abuse of the garbage collector". I'd put it the other way around ...)
Our initial tag engine design was a GC nightmare. The worst possible type memory allocation. Lots of objects with lots of references that lived just enough time to get into generation 2 (which was collected every couple of minutes on our web servers).
Interestingly, the worst possible scenario for the GC is quite common in our environment. We quite often cache information for 1 to 5 minutes.
(Curiously, this is under a header mentioning "abuse of the garbage collector". I'd put it the other way around ...)