| Stuck on 63% [message #3187] |
Mon, 25 August 2008 17:16  |
Eclipse User |
|
|
|
Originally posted by: tweakmonkey78.hotmail.com
I have an 800MB dump and I'm running the standalone Memory Analyzer with
-Xmx1340M but the this doesn't seem to be enough as it always gets stuck
at 63% complete with the CPU at 99%. So after about 20 minutes at 63% I
always kill the process.
What I'd like to know is am I doing something wrong? And when will there
be a ScriptParseHeapDump.bat and console mode the way there was in the old
SAP version? All I want to do is get the dump parsed once!
Cheers
|
|
|
|
| Re: Stuck on 63% [message #3323 is a reply to message #3223] |
Tue, 26 August 2008 14:03  |
| Eclipse User |
|
|
|
Originally posted by: tweakmonkey78.hotmail.com
Andreas Buchen wrote:
> The size of the dump is not really relevant, it's the number of objects.
> The number of objects hurts when transforming the object graph into the
> dominator tree... So if this case does not exhibit a large number of
> objects, let me know. A rule of thumb is 30 million should be okay on
> 32bit, but it also depends on the shape of the graph.
> With the latest version, you should be able to say on the command line:
> MemoryAnalyzer.exe -application org.eclipse.mat.api.parse <path/to/heap>
Thanks - I really like being able to parse the dump from the command line.
I left it running yesterday evening and it finished in just over 2 hours.
There are 25.5M objects. I'm puzzled why it takes so long as my old
version 1.1.1 of SAP Memory Analyzer (using ScriptParseHeapDump.bat) could
do it in 12 minutes.
Anyway at last I can use the GUI and I must say it's superb. Keep up the
good work!
|
|
|
| Re: Stuck on 63% [message #5987 is a reply to message #3187] |
Thu, 30 October 2008 01:29 |
| Eclipse User |
|
|
|
Originally posted by: eclipse_org.414n.net
I ran into the same problem. My heap dump was 1.5G with 19 million
objects.
I looked at the thread stack traces with JConsole and one of the workers
was stuck at org.eclipse.mat.collect.SetInt.add.
I replaced the implementation of SetInt with IntHashSet from
http://www.sosnoski.com/opensrc/tclib/
I renamed it, added an iterator and toArray method, compiled it plus its
two ancestor classes, and dropped it in the jar file.
After this it analyzed the heap dump in maybe 5 minutes.
Aside from this issue, I really like the tool. The UI and analysis modes
are good and the memory usage is 1G vs 8G or more for the others I have
tried.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03071 seconds
] 
Search
Help
Register
Login
Home
