Original link: Stop Wasting Memory: 5 Advanced .NET Tricks Nobody Teaches You / Stackademic.
Low level stuff is always interesting. But I am not too happy about this one.
All of the 5 recommendations makes the code more difficult to read and understand. None of them should be done unless there is hard evidence that it will actually improve overall performance of the application significantly. I miss some disclaimer.
And I don't think the last 2 recommendations are well described. Object pools are usualy an anti-pattern in systems with generational garbage collection. GC of objects in young generation is extremely fast. So allocating many objects in a tight loop will actually be faster than borrowing objects from a pool. If the proposed pool solution is faster, then it is not due to new+GC overhead, but because reusing the same piece of memory over and over again is more cache friendly than allocating new memory and using that for every iteration. All this is missing in the article.