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: | Tabular version of Thread State information | ||
---|---|---|---|
Product: | profiler | Reporter: | _ gsporar <gsporar> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ gsporar
2007-04-11 20:00:06 UTC
Implemented as a table with columns containing both absolute and relative times for each thread state - I'm not sure if extra columns for percentage values are really useful. Let's evaluate users feedback and eventually add the percentage bars later. Implemented for 6.5 M2. changeset: 87583:767a33c9a90b date: Fri Jul 04 17:58:45 2008 +0200 summary: Implemented #100662: Tabular version of Thread State information changeset: 87584:f6eeb993d8ef date: Fri Jul 04 23:17:35 2008 +0200 summary: Missing file for #100662 implementation Integrated into 'main-golden', available in NB_Trunk_Production #305 build Changeset: http://hg.netbeans.org/main/rev/767a33c9a90b User: Jiri Sedlacek <jis@netbeans.org> Log: Implemented #100662: Tabular version of Thread State information >I'm not sure if extra columns for percentage values are really useful. The use case I was thinking of was an application with a large number of threads (thousands of threads). If I want to see the threads that spent a large percentage of their time in a particular state, then I need the ability to sort on percentage. So for example, if thread A spent 45 seconds of its 2 hour life in Monitor mode and thread B spent 10 seconds of its 11 second life in Monitor mode when I click the Monitor column, thread A will always be listed *before* thread B (when sorted in descending order). But thread B (and similar threads: short life, but much of it in Monitor mode) is what I might need to see - because it spent a large percentage of its time in Monitor mode. In other words, since threads can live for such widely varying amounts of time, the ability to sort just by percentage could be convenient. >Let's evaluate users feedback Agreed. :-) >and eventually add the percentage bars later. I'm not sure I understand this: "percentage bars." Did you mean "percentage column"? |