Bug 234123 - [Heapwalker] Improve performance of JavaClass.getInstances()
[Heapwalker] Improve performance of JavaClass.getInstances()
Status: RESOLVED FIXED
Product: profiler
Classification: Unclassified
Component: Engine
7.2
All All
: P3 (vote)
: 7.4
Assigned To: Tomas Hurka
issues@profiler
: PERFORMANCE, VISUALVM
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-08 08:59 UTC by Tomas Hurka
Modified: 2013-08-19 02:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Hurka 2013-08-08 08:59:34 UTC
Currently JavaClass.getInstances() starts search for instances at the beginning of instance dump segment. It is possible to remember offset of the first instance and start search from that offset. This will improve performance of JavaClass.getInstances() on big heap dumps for classes with instances, which are close to each other and for all classes with one instance.
Comment 1 Tomas Hurka 2013-08-08 09:28:19 UTC
Fixed in profiler-main

changeset:   260483:37e19fa1dece
user:        Tomas Hurka <thurka@netbeans.org>
date:        Thu Aug 08 11:02:46 2013 +0200
summary:     bugfix #234123, search for the instances from the offset of the first instance
Comment 2 Quality Engineering 2013-08-19 02:22:49 UTC
Integrated into 'main-silver', will be available in build *201308182300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/37e19fa1dece
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #234123, search for the instances from the offset of the first instance


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