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 55202 - Ability to do line-by-line code fragment profiling
Summary: Ability to do line-by-line code fragment profiling
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-18 17:23 UTC by iformanek
Modified: 2007-03-23 15:03 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-02-18 17:23:26 UTC
A special version of code fragment profiling, 
that provides timing of each line of specific 
method(s).

Obviously, not all lines are good candidates, so 
limiting this to method calls and loops would 
allow to keep the interference of a reasonable 
level.

I've used this approach frequently when trying to 
determine why certain method is slow - simply put 
System.currentTimeMillis on several line within a 
method to determine, which is the offending line 
(usually which is the offending method call).
Comment 1 iformanek 2005-03-29 14:57:10 UTC
Not planned for 1.0
Comment 2 Jiri Sedlacek 2007-03-23 15:03:38 UTC
Can be done using Stopwatch Profiling Point.