Re: Memory Profiler for Heap Analysis
- From: "Moritz Wissenbach" <m._N0_SPM_wissenbach@xxxxxx>
- Date: Wed, 13 Jun 2007 15:09:22 +0200
On Wed, 13 Jun 2007 14:09:31 +0200, Robert Klemme <shortcutter@xxxxxxxxxxxxxx> wrote:
this exists, how does it properly calculate sizes? How many levels does it follow when counting?Until it hits a cycle?
If it does not?
Well, then all the better: it's a proper tree and at some point you'll have traversed it completely.
How do you count objects that are referenced by multiple other instances etc.Add the objects size to both instaces...?
Remember that n is not restricted to 2, could be much higher.
The point you're interested in is the size of a certain object, say A. You go ahead and look at what other objects it points. Say it points to object B. Since A points to B, B's size needs to be added to A's size. It doesn't matter what other objects point to B, for it will always be referenced from A, thus, is part of A no matter what.
On the other hand: I'm looking for things to REMOVE from the program. So, if you would remove A in the above scenario, B would still remain in memory, so it would be misleading.
Oh well. If we continue discussing, we could as well implement it. Are you in ? ;)
DOM is a good candidate. If I were you, I'd create an application object model, throw away the DOM parsing and create a SAX parser which directly creates the model. Just my 0.02 EUR...
I think the things we want to achieve (online validation for example) do require a DOM...
It's just frustrating. I have the heap dump in front of my eyes, I can see all the classes of the DOM, still I can't figure out just how much of the memory they cost in total.
Moritz
.
- Follow-Ups:
- Re: Memory Profiler for Heap Analysis
- From: Robert Klemme
- Re: Memory Profiler for Heap Analysis
- From: Lew
- Re: Memory Profiler for Heap Analysis
- References:
- Memory Profiler for Heap Analysis
- From: Moritz Wissenbach
- Re: Memory Profiler for Heap Analysis
- From: Robert Klemme
- Re: Memory Profiler for Heap Analysis
- From: Moritz Wissenbach
- Re: Memory Profiler for Heap Analysis
- From: Robert Klemme
- Memory Profiler for Heap Analysis
- Prev by Date: Re: Drawing problems
- Next by Date: Re: Drawing problems
- Previous by thread: Re: Memory Profiler for Heap Analysis
- Next by thread: Re: Memory Profiler for Heap Analysis
- Index(es):
Relevant Pages
|