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.

Bug 66475 - Instrumenting getters/setters in Entire Application profiling can have negative effect on the results
Summary: Instrumenting getters/setters in Entire Application profiling can have negati...
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-11 13:36 UTC by iformanek
Modified: 2007-02-20 18:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-10-11 13:36:46 UTC 
The Entire Application profiling does instrument simple methods that only 
access a field (getters/setters). The results can be negatively affected by 
this, if the simple methods are called very frequently.

The default should change not to include getters/setters and/or possibly not 
take timestamps with simple methods to lower the overhead proportions.
Comment 1 iformanek 2005-10-11 16:00:26 UTC 
Fixed in M10
Comment 2 ehucka 2005-10-20 14:45:45 UTC 
Is it possible to not instrument methods like:
JComponent.getWidth() {super.getWidth();} and the super defines getWidth()
{return width;} ?
It is getter but it is always instrumented.
Comment 3 iformanek 2005-10-20 17:40:19 UTC 
Yes, I am thinking along the same lines to extend the instrumentation exclusion 
to a more broadly defined "simple" methods, perhaps with user-customizable 
level of complexity.

Currently this is not possible to do easily though, so not for 1.0
Comment 4 ehucka 2006-10-09 12:10:17 UTC 
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-20 10:27:34 UTC 
Closing old issues
Comment 6 Alexander Kouznetsov 2007-02-20 18:10:51 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.