Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "TPTP Profiling Initiative Feedback Summary"

(Feedback)
(User Feedback)
 
(13 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
During the development of TPTP v4.5.2 iteration 1 and 2, invitation was sent to the TPTP and Eclipse communities targeting plug-in developers to evaluate the TPTP driver and feedback for improvement. This page summaries the feedback collected and tracks the defects opened to address the problem.
 
During the development of TPTP v4.5.2 iteration 1 and 2, invitation was sent to the TPTP and Eclipse communities targeting plug-in developers to evaluate the TPTP driver and feedback for improvement. This page summaries the feedback collected and tracks the defects opened to address the problem.
  
== Feedback ==
+
== User Feedback ==
  
 
{| border="1" cellpadding="2" |
 
{| border="1" cellpadding="2" |
Line 9: Line 9:
 
!width="200" style="background:mediumslateblue; color:white"|Defects
 
!width="200" style="background:mediumslateblue; color:white"|Defects
 
|-
 
|-
|col1
+
|Installation/Setup: Missing dependencies indication
 +
: * It is not clear to user what to select in  the list features in order to install profiling support.
 
|
 
|
* I've added TPTP to my current Eclipse Ganymede, using p2. First I  
+
* "I've added TPTP to my current Eclipse Ganymede, using p2. First I  
 
installed only profiling feature and I had no monitors available. I then  
 
installed only profiling feature and I had no monitors available. I then  
 
installed all in TPTP group in p2 install manager and was finally able  
 
installed all in TPTP group in p2 install manager and was finally able  
 
to use Java profiling monitors (execution time, memory, thread, probe  
 
to use Java profiling monitors (execution time, memory, thread, probe  
 
insertion). I have no idea which package should I have chosen to have  
 
insertion). I have no idea which package should I have chosen to have  
monitors at the beginning. This may be issue for someone new to TPTP.
+
monitors at the beginning. This may be issue for someone new to TPTP."
|col3
+
|[https://bugs.eclipse.org/259184 bug 259184]
 
|-
 
|-
|col1
+
|Agent action: Refresh vs Refresh view vs Unload Profiling Data
 +
: * Revisit the actions and display strings used.
 
|
 
|
* Trying to figure out how to get any profiling information, I went to  
+
* "Trying to figure out how to get any profiling information, I went to  
 
Profiling Monitor view, right clicking on different elements and  
 
Profiling Monitor view, right clicking on different elements and  
 
pressing "Refresh" from context menu. It was asking whether to refresh  
 
pressing "Refresh" from context menu. It was asking whether to refresh  
Line 28: Line 30:
 
Suddenly after one of those refreshes, everything had disappeared in  
 
Suddenly after one of those refreshes, everything had disappeared in  
 
Profiling Monitor - like the projects were removed, and after a while I  
 
Profiling Monitor - like the projects were removed, and after a while I  
got NPE (it was happening during profiling session)
+
got NPE (it was happening during profiling session)"
 
+
|[https://bugs.eclipse.org/bugs/show_bug.cgi?id=259186 bug 259186]
* It's hard to find filters settings window. It would be also cool if
+
the view had automatically showed, which classes and packages will be
+
filtered with current filter settings. (e.g. by using packages and
+
classes available in workspace). Without that, user has to spend 2-3
+
profiling sessions just to tune the filters.
+
|col3
+
 
|-
 
|-
|col1
+
|Statistics View: Maintain expanded node
 +
: * Persists user selection and tree state.
 
|
 
|
* Execution statistics view is hard to use during profiling session,  
+
* "Execution statistics view is hard to use during profiling session,  
because whenever I expand some tree node, it's collapsed immediately.
+
because whenever I expand some tree node, it's collapsed immediately."
|col3
+
|[https://bugs.eclipse.org/bugs/show_bug.cgi?id=259189 bug 259189]
 
|-
 
|-
|col1
+
|Statistics View: Maintain column width
 +
: * Remember user customization on view attributes, eg column width.
 
|
 
|
* Execution statistics viewer again. Columns don't remember their width  
+
* "Execution statistics viewer again. Columns don't remember their width  
 
settings. When I switch e.g. between Package and Class level  
 
settings. When I switch e.g. between Package and Class level  
 
information, columns restore to their original sizes. Generally columns  
 
information, columns restore to their original sizes. Generally columns  
 
could be wider - specially Package column (it's normal to have package  
 
could be wider - specially Package column (it's normal to have package  
 
longer than 15 chars) and calls (it's normal to have more than 100000  
 
longer than 15 chars) and calls (it's normal to have more than 100000  
calls.
+
calls."
* Execution statistics view could be easier to use - e.g. don't collapse
+
|[https://bugs.eclipse.org/bugs/show_bug.cgi?id=259195 bug 259195]
profiling details nodes during profiling session, columns width should
+
be remembered.
+
|col3
+
 
|-
 
|-
 
|Documentation Improvement : filter configuration
 
|Documentation Improvement : filter configuration
 +
: * Add some sort of user guidance on filter configuration, eg. pop up dialog.
 
|
 
|
* It's not obvious where to find filters configuration in Monitor. (You  
+
* "It's not obvious where to find filters configuration in Monitor. (You  
 
have to click "Edit Options" on Java profiling node in Monitor tab in  
 
have to click "Edit Options" on Java profiling node in Monitor tab in  
launch configuration).
+
launch configuration). It's not obvious why there are no filtering  
It's not obvious why there are no filtering results, when launching  
+
results, when launching  
profiling with default settings.
+
profiling with default settings."
|col3
+
* "It's hard to find filters settings window. It would be also cool if
 +
the view had automatically showed, which classes and packages will be
 +
filtered with current filter settings. (e.g. by using packages and
 +
classes available in workspace). Without that, user has to spend 2-3
 +
profiling sessions just to tune the filters."
 +
|TODO
 
|-
 
|-
 
|Documentation Improvement : Memory consumption
 
|Documentation Improvement : Memory consumption
 +
: * Document the additional requirement on memory consumption by profiler.
 
|
 
|
* If TPTP requires additional memory, it'd be good to have that documented  
+
* "If TPTP requires additional memory, it'd be good to have that documented  
 
somewhere or have some message dialog popping out. Eclipse SDK defaults  
 
somewhere or have some message dialog popping out. Eclipse SDK defaults  
are not enough (256M for heap).
+
are not enough (256M for heap)."
|col3
+
|TODO
 
|}
 
|}
  

Latest revision as of 18:26, 22 December 2008

Background

During the development of TPTP v4.5.2 iteration 1 and 2, invitation was sent to the TPTP and Eclipse communities targeting plug-in developers to evaluate the TPTP driver and feedback for improvement. This page summaries the feedback collected and tracks the defects opened to address the problem.

User Feedback

Issues User Descriptions Defects
Installation/Setup: Missing dependencies indication
* It is not clear to user what to select in the list features in order to install profiling support.
  • "I've added TPTP to my current Eclipse Ganymede, using p2. First I

installed only profiling feature and I had no monitors available. I then installed all in TPTP group in p2 install manager and was finally able to use Java profiling monitors (execution time, memory, thread, probe insertion). I have no idea which package should I have chosen to have monitors at the beginning. This may be issue for someone new to TPTP."

bug 259184
Agent action: Refresh vs Refresh view vs Unload Profiling Data
* Revisit the actions and display strings used.
  • "Trying to figure out how to get any profiling information, I went to

Profiling Monitor view, right clicking on different elements and pressing "Refresh" from context menu. It was asking whether to refresh from file system or don't refresh from FS (it is not intuitive for me what should I choose, as I don't know what is written to file system). Suddenly after one of those refreshes, everything had disappeared in Profiling Monitor - like the projects were removed, and after a while I got NPE (it was happening during profiling session)"

bug 259186
Statistics View: Maintain expanded node
* Persists user selection and tree state.
  • "Execution statistics view is hard to use during profiling session,

because whenever I expand some tree node, it's collapsed immediately."

bug 259189
Statistics View: Maintain column width
* Remember user customization on view attributes, eg column width.
  • "Execution statistics viewer again. Columns don't remember their width

settings. When I switch e.g. between Package and Class level information, columns restore to their original sizes. Generally columns could be wider - specially Package column (it's normal to have package longer than 15 chars) and calls (it's normal to have more than 100000 calls."

bug 259195
Documentation Improvement : filter configuration
* Add some sort of user guidance on filter configuration, eg. pop up dialog.
  • "It's not obvious where to find filters configuration in Monitor. (You

have to click "Edit Options" on Java profiling node in Monitor tab in launch configuration). It's not obvious why there are no filtering results, when launching profiling with default settings."

  • "It's hard to find filters settings window. It would be also cool if

the view had automatically showed, which classes and packages will be filtered with current filter settings. (e.g. by using packages and classes available in workspace). Without that, user has to spend 2-3 profiling sessions just to tune the filters."

TODO
Documentation Improvement : Memory consumption
* Document the additional requirement on memory consumption by profiler.
  • "If TPTP requires additional memory, it'd be good to have that documented

somewhere or have some message dialog popping out. Eclipse SDK defaults are not enough (256M for heap)."

TODO






Back to TPTP wiki page

Back to the top