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 105544 - ms vs. µs
Summary: ms vs. µs
Status: VERIFIED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-04 11:11 UTC by Alexander Kouznetsov
Modified: 2007-10-01 10:51 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 Alexander Kouznetsov 2007-06-04 11:11:32 UTC 
NetBeans IDE Dev (Build 200705311200)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

There is a following inconsistency in profiler UI: ms units are used for Live
Results and CPU snapshots while µs units are used for Stopwatch Profiling Point
results. I believe that the style needs to be unified.
Comment 1 Jiri Sedlacek 2007-10-01 10:38:53 UTC 
This is intentional - whereas "normal" cpu results have ms accuracy, Stopwatches as a future replacement for Code
fragment profiling have µs results accuracy. This is also by usecase - "normal" results are for evaluation/detecting
problems, Stopwatches as a future replacement for Code fragment profiling are for example for fine-tuning algorithms.
Comment 2 Alexander Kouznetsov 2007-10-01 10:51:34 UTC 
Its up to you. I believe that having different units is disappointing. The accuracy can be shown just with digits after
decimal dot like 1.508 ms, for example.