Bug 212480 - Memory profiling imposes too much overhead in the profiled application
Memory profiling imposes too much overhead in the profiled application
Status: STARTED
Product: profiler
Classification: Unclassified
Component: Base
7.2
All All
: P3 (vote)
: 7.3
Assigned To: Tomas Hurka
issues@profiler
: 7.2_WAIVER_APPROVED
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-14 13:43 UTC by Jiri Sedlacek
Modified: 2012-10-31 14:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments
Initial prototype (23.32 KB, patch)
2012-09-14 07:31 UTC, Tomas Hurka
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Sedlacek 2012-05-14 13:43:49 UTC
See the bugdb for details:

"Used IDE profiler to memory profile IDE itself. It takes a very long time to start, around ten minutes - this makes it almost unusable for large projects like this."
Comment 1 Tomas Hurka 2012-09-14 07:31:09 UTC
Created attachment 124348 [details]
Initial prototype
Comment 2 Petr Cyhelsky 2012-10-31 14:28:21 UTC
This issue was partially fixed by fixing of issue #217458 (implementation of memory sampler) thus this issue is not so important now


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo