Community
Participate
Working Groups
When there is no profiling data of a selected resource. Subject views should show an empty gray page with message stating that there is no data available and show user option to select to enable data collection.
If this Bugzilla is planed to be completed in 4.5, please add the plan keyword. Otherwise, please target to future. In addition, if this Bugzilla is committed to be completed in 4.5, please change the priority to P1.
Eugene, could you clarify what do you mean? Currently if user opens trace without sutable data, new gray page is opened with "No data is available for display..." message.
With Link with Viewer button enabled, profiling with Memory Analysis shows Execution Statistics with packages and classes in zero values. Similarly, profiling with Thread Analysis shows Object Allocations with zero value entries. In Long run, I suggest to place the session summary page as a common page for all statistics views as it contains more than one specific type of trace event.
(In reply to comment #3) > With Link with Viewer button enabled, profiling with Memory Analysis shows > Execution Statistics with packages and classes in zero values. > Similarly, profiling with Thread Analysis shows Object Allocations with zero > value entries. > > In Long run, I suggest to place the session summary page as a common page for > all statistics views as it contains more than one specific type of trace event. > Eugene, it is good idea to make one common page for all types of profiling. But currently we have two versions of Session Summary page. One is used for PI traces. It contains tables with top 10 for execution and top 10 for heap. Another is used for TI and contains only execution top 10. Both can't be used anyhow for thread profiler trace and don't look meaningful if contain zeros without any notes. Gray page with explanation for user looks more helpful for me, maybe text on it can be revisited. But we can go further with your idea. I propose to add new session summary page. It should not contain any strange top 10 statistics but real session summary :) like: - duration of profiling session - profiling options - JVM options - used Filters - types of profiling data available in trace - host - custom comments to trace - whatever you want :) So, could we close this bug (if we are not going to change anything on gray page), and open bug for new session summary page.
Alex, I like the idea of a true summary page about the tracing itself, not on the data collected. That is something we have on the trace properties dialog (properties under context menu of host,process, and agent) but having a dedicated view for this data is a good idea. Could you open a separate enh for this? With respect to the original problem reported here: 1.With Link with Viewer button enabled, profiling with Memory Analysis shows Execution Statistics with packages and classes in zero values. 2.Similarly, profiling with Thread Analysis shows Object Allocations with zero value entries. I suggest to show the default page for the above use cases where there is no meaningful data but zero values.
> With respect to the original problem reported here: > 1.With Link with Viewer button enabled, profiling with Memory Analysis shows > Execution Statistics with packages and classes in zero values. > 2.Similarly, profiling with Thread Analysis shows Object Allocations with zero > value entries. > I suggest to show the default page for the above use cases where there is no > meaningful data but zero values. > Eugene, I am not sure what such solution will not get user wrong experience. He may think what reason of zeros in views is misconfiguration of profiling, incorrect filters or application failure. But at the same time be sure what correct data can be seen in view if profiling run correctly. So better don't mislead users. We have two types of traces on Profiling Monitors view: 1. trace collected in WB with know type of profiling 2. trace imported from file without distinct type For case 1 always open view of corresponding type (by double click or from context menu), even if no data for it were collected (Thread, Heap or Execution statistics with zeros). For case 2 show gray page with note for user. IMHO Session summary don't make any sense even with data. It just duplicates next tab but with some filtering. Thanks, Alex.
Alex, I think there is some miscommunication here. I was not referring to the session summary TAB when I stated the problem: > With respect to the original problem reported here: > 1.With Link with Viewer button enabled, profiling with Memory Analysis shows > Execution Statistics with packages and classes in zero values. When user collects only Memory Analysis, Execution Statistics TAB under Execution Statistics VIEW should shows default gray page, instead of zero entries. > 2.Similarly, profiling with Thread Analysis shows Object Allocations with zero > value entries. When user collects only Thread Analysis, Object Allocations VIEW should show gray page, instead of zero entries. > I suggest to show the default page for the above use cases where there is no > meaningful data but zero values. > Session summary was a separate discussion to the original problem reported here. I raised it because it's a tab of the Execution Statistics VIEW which is not applicable for all analysis type actually.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
