Community
Participate
Working Groups
The current Profiling Monitors view provides a host/node oriented view using the structure: Folder Monitor Node Agent The structure of the view can be simplified by providing a more application-oriented approach to viewing profiling/monitoring. However, users could optionally re-organize the view to the traditional node/host-oriented approach using the triangle drop-down in the view. This new organization of the view would provide more consistency with the Eclipse Debug perspective, and can help simplify the conceptual model of monitoring/profiling for the user. The possible application-oriented structure is: Application/Launch Profiling target (target, hostname, Process ID) Agent Agent details (optional) Other objects such as heapdumps, etc. can also be included under a given profiling target. An example of the structure: HelloWorld [Java Application] HelloWorld at localhost [ PID:2252 ] <Monitoring> Profiling Execution time analysis Memory/heap analysis In the figure below, the user has launched the Java application "HelloWorld" and is monitoring/profiling. The user has selected to enable Execution time analysis and Memory/heap analysis and the profiling types are displayed under the agent.
Changing target to future. A number of smaller related enhancements are being made for M9 related to this enhancement such as Bug 58363 until there is time to resolve this issue and more time to finalize the correct design.
This feature should also cover the workload grouping from PPA.
Targeted to 4.0 by the requirements team. Please create a description document in CVS.
My understanding is this should cover usability features from PPA Profiling projects view, including user labeling of resources presented in the profiling monitor view tree. That is its not related to the workload grouping from PPA.
Update target to 3.3 based on TPTP Features for 3.2+ document Feature committed to 3.3
Updating feature target per 01/10 UI main committers meeting
The outcome from the meeting on this feature was the following: The only thing that will change for this one is to replace the individual navigator filters (i.e. for monitor/host/process/agent) with two layouts. One for application-oriented profiling and the other for distributed profiling. The application oriented one will be the same as what is now the default in the profiling monitor view, and the distributed one will unfilter everything, as if you manually unfiltered the hosts and monitors. It is still not decided what these layouts/groups will be called. A more important feature which was pointed out was 58385, which is not yet committed.
Feature completed and submitted to 3.3 and 4.0.
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.
