This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Profiler unable to handle large heap dumps | ||
---|---|---|---|
Product: | profiler | Reporter: | Petr Nejedly <pnejedly> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Petr Nejedly
2008-06-06 18:34:27 UTC
Now I have realized that in my case (1.3GB heap dump), the profiler fell back (through OOME) to the file implementation of the index, thus making part of my claims inaccurate, but also making the slowness even more pronounced - the profiler tried to build a 300MB+ index file by randomly seeking all over the place and rewriting small chunks of data all the time. No wonder it was that slow! I am sorry this not a bug report. The situation with memory mapping is not that simple as you think. Both implementation (memory mapped and plain file I/O) is available depending on size of available memory. According my tests memory mapping is faster. Opening heap dump on linux is known to be slower that on other OSes. |