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 179182 - 'Time spend' field of slowness reports shows odd values
Summary: 'Time spend' field of slowness reports shows odd values
Status: RESOLVED DUPLICATE of bug 199372
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-04 05:59 UTC by Jan Stola
Modified: 2014-03-05 14:07 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 170555


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Stola 2010-01-04 05:59:56 UTC
The 'Time spend' field of slowness reports sometimes shows much bigger values than is the length of the corresponding snapshot. See, for example, http://statistics.netbeans.org/exceptions/exception.do?id=322280 The 'Time spend' is ~26s, but the length of the snapshot is ~16s.
Comment 1 Jindrich Sedek 2010-01-12 02:14:08 UTC
I expect the problem is that we start sampling after noticing some problem, so it doesn't run immediatelly from the beggining of the blockage. The 'time spent' should mean the real time spent, but the snapshot covers just a part of it. 

The question is why there is so big difference. Might the self sampler action inicialization take so much time?
Comment 2 Tomas Pavek 2010-04-01 15:30:07 UTC
The given example is ok - the 10s difference is normal for NB 6.8 release builds where sampling starts after 10s (and reported when overall time exceeds 20s).
Would be good to identify some other examples.

BTW seems there's some problem since about 100226 in snapshots from code completion - they have completely wrong overall time (e.g. like 7 digit numbers).
See e.g.
http://statistics.netbeans.org/exceptions/detail.do?id=164422
Jarda is fixing this particular case.
Comment 3 Jan Stola 2010-04-06 12:25:04 UTC
> The given example is ok - the 10s difference is normal
> for NB 6.8 release builds where sampling starts after
> 10s (and reported when overall time exceeds 20s).

OK, while I am still not comfortable with such partial
reports, I understand that a difference of 10s is 'as designed'.

So, what about
http://statistics.netbeans.org/exceptions/exception.do?id=365936
time spent: 27.3s, the length of the snapshot: 9.5s. Is this one
caused by another hidden feature that I am not aware of? ;o)
Comment 4 Tomas Pavek 2010-06-09 11:52:59 UTC
Or this report that came today: invocation time 18097ms, then in the snapshot 26.7ms.
http://statistics.netbeans.org/exceptions/exception.do?id=399943

Other such examples:
http://statistics.netbeans.org/exceptions/exception.do?id=395365
http://statistics.netbeans.org/exceptions/exception.do?id=397732
http://statistics.netbeans.org/exceptions/exception.do?id=392889

Should not such snapshots be discarded and not sent anywhere?
Comment 5 Petr Cyhelsky 2014-03-05 14:07:51 UTC

*** This bug has been marked as a duplicate of bug 199372 ***