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.
Summary: | Bar and value columns in CPU and Memory snapshots should be called differently in header popup. | ||
---|---|---|---|
Product: | profiler | Reporter: | ehucka <ehucka> |
Component: | Base | Assignee: | Jiri Sedlacek <jis> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | Keywords: | VISUALVM |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ehucka
2006-11-22 14:24:32 UTC
The problem is that the bar doesn't display percentage values - highest value (for example 50%) is displayed as full-length bar and other bars are representing relative difference to that value. The [%] sign could thus be misleading. One possibility is to rename the column to 'Bytes Allocated (rel)', but this is too long and would be problematic for Memory Liveness results where many columns have to be visible. Closing as wontfix for now as no problems with column name have been experienced and the bar itself seems to be self-explaining enough. verified There is an inconsistency between Memory and CPU snapshot tables, both having the same columns, but called and scaled differently. The same column for CPU snapshot is shown with "[%]" suffix and the bars are scaled so 100% is the whole column width. I don't want to reopen this issue since I can't define which approach is better but I would like to see consistency between two snapshot UIs. I would like to recommend to add "(bar)" and "(number)" suffixes to menu items in Hide or Show columns popup and leave column names unchanged. And make CPU snapshot to use the same scaling for bars. I agree with identifying the columns as "(bar)" and "(value)" in header popup, it is reasonable and useful. But I'm not sure I agree what do you mean by "make CPU snapshot to use the same scaling for bars". The same as what? For memory snapshot the following rule is used: (citing) highest value (for example 50%) is displayed as full-length bar and other bars are representing relative difference to that value. For CPU snapshots, full-length bar is representing 100% value, not the highest value. This is the inconsistency I'm talking about, and I like the approach used for memory snapshots. Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode. Milestone cleanup: future->next Addressed by adding [%] badge to memory views and switching to percentage bars for both CPU and memory results. Fixed by http://hg.netbeans.org/profiler-main/rev/13c9c1bfaf94. Integrated into 'main-golden', will be available in build *201208280001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/13c9c1bfaf94 User: Jiri Sedlacek <jis@netbeans.org> Log: Bugfix #89861 - percentage bar for memory results, [%] badge for bar column |