A resource like memory is often the most scarce in high-end applications, reason why its critical to detect and optimize bottlenecks under such circumstances. This post by Markus Kohler explores the concepts of garbage collection, retained set and dominator tree -- applied to memory optimization -- using the Eclipse Memory Analyzer. Read Markus Kohler post 'How to really measure the memory usage of your objects': http://kohlerm.blogspot.com/2009/02/how-to-really-measure-memory-usage-of.html
- Posted by: Daniel Rubio
- Posted on: February 10 2009 06:57 EST
Thanks, I guess this should motivate me to describe the dominator tree and it's advantages in more detail in a follow up post :) Regards, Markus
Check "Memory leaks are easy to find" at http://kohlerm.blogspot.com/2009/02/memory-leaks-are-easy-to-find.html
Very interesting article. I have written on the difficulty to measure an object graph size, applied to the HttpSession. Shameless plug: a good tool to measure your HttpSession sizes is MessAdmin (open-source, production-ready). It does much more than that of course, but that would get out of the scope of this article!