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.
Difference between revisions of "TPTP User Experiences Profiling"
(→Contact points) |
(→Ideal Candidate Criteria For This Survey) |
||
Line 12: | Line 12: | ||
=== Ideal Candidate Criteria For This Survey === | === Ideal Candidate Criteria For This Survey === | ||
− | The tptp team is undertaking an effort to improve the | + | The tptp team is undertaking an effort to improve the usability and out-of-the-box experience for the profiler. We are going to do that by working closely with some lead users. The term lead user comes from the work of Eric von Hippel at MIT. The lead users will use the tptp profiler and will be closely supported by the tptp team. The lead users will get usage (and bug) feedback to the tptp team, who will expedite the resolution of issues. The lead user would expect to get a number of deliveries of the profiler during the course of their usage, each improving on the usability and out-of-the-box experience. The lead user may be given prototypes to try. It is anticipated that tptp will work with a number of lead users. Our desire is to get an improved user experience into Gannymede. |
Here are the characteristics of the ideal lead user. | Here are the characteristics of the ideal lead user. | ||
− | * The lead user's application runs on the tptp reference platform | + | * The lead user's application runs on the tptp reference platform: Windows XP and the IBM JVM 1.5. We will also consider other 1.5 JVMs. |
− | * To make debugging and support simpler, the lead user's application | + | * To make debugging and support simpler, the lead user's application is easily executed by the tptp test team on their system (the reference platform). This implies that there should not be a lot of external "strange" dependencies in the lead user's application, as the tptp team will not be able to easily recreate the lead user's environment. |
If you would like to be a lead user, email alexander.n.alexeev@intel.com | If you would like to be a lead user, email alexander.n.alexeev@intel.com | ||
− | Below | + | Below is a more formal definition of "strange" for a lead user's project. These are not mandatory but help understand our position. |
Anyway, please contact, and we will try to find convenient cooperation process. | Anyway, please contact, and we will try to find convenient cooperation process. | ||
(in priority order): | (in priority order): | ||
− | |||
* Doesn't require third party's software | * Doesn't require third party's software | ||
− | * Can work on single computer, doesn't require distributed environment. | + | * Can work on single computer, doesn't require distributed environment. Can access the Internet. |
* Easy to deploy | * Easy to deploy | ||
− | * Isn't very specific application field. | + | * Isn't a very specific application field. The purpose and use cases are understandable without special knowledge. This will result in a short time for the tptp team to familiarize themselves with the application. |
* Absence or minimum of native libraries | * Absence or minimum of native libraries | ||
* Can be downloaded from CVS and built from scratch in Eclipse | * Can be downloaded from CVS and built from scratch in Eclipse | ||
− | |||
== J2EE == | == J2EE == |
Revision as of 12:46, 13 November 2007
Note that when you edit a page on the wiki, there is a checkbox you can click to be notified of updates to the page. E-mail notification should be turned on at your Wiki Preferences, "my preferences" at top of page. I'm not 100% sure if it works but if it does, it will be a good way to avoid having to cc a mailing list whenever you update the wiki...
Please use Discussion page for suggestions, questions and thoughts
This page discusses user types that we are hoping to solicit feedback regarding user experiences. In particular, we hope to get pointed feedback and make TPTP better for these classes of users.
Contents
Come to TPTP as Lead user
J2SE
J2SE 5 and J2SE 6 are supported in TPTP by the new JVMTI interface while J2SE 1.4 and below are supported using the old JVMPI interface. The components of TPTP profiler that are evolving the most relate to the JVMTI profiling experience. If you don't know what version of Java you are using, please use java -version.
Ideal Candidate Criteria For This Survey
The tptp team is undertaking an effort to improve the usability and out-of-the-box experience for the profiler. We are going to do that by working closely with some lead users. The term lead user comes from the work of Eric von Hippel at MIT. The lead users will use the tptp profiler and will be closely supported by the tptp team. The lead users will get usage (and bug) feedback to the tptp team, who will expedite the resolution of issues. The lead user would expect to get a number of deliveries of the profiler during the course of their usage, each improving on the usability and out-of-the-box experience. The lead user may be given prototypes to try. It is anticipated that tptp will work with a number of lead users. Our desire is to get an improved user experience into Gannymede.
Here are the characteristics of the ideal lead user.
- The lead user's application runs on the tptp reference platform: Windows XP and the IBM JVM 1.5. We will also consider other 1.5 JVMs.
- To make debugging and support simpler, the lead user's application is easily executed by the tptp test team on their system (the reference platform). This implies that there should not be a lot of external "strange" dependencies in the lead user's application, as the tptp team will not be able to easily recreate the lead user's environment.
If you would like to be a lead user, email alexander.n.alexeev@intel.com
Below is a more formal definition of "strange" for a lead user's project. These are not mandatory but help understand our position. Anyway, please contact, and we will try to find convenient cooperation process.
(in priority order):
- Doesn't require third party's software
- Can work on single computer, doesn't require distributed environment. Can access the Internet.
- Easy to deploy
- Isn't a very specific application field. The purpose and use cases are understandable without special knowledge. This will result in a short time for the tptp team to familiarize themselves with the application.
- Absence or minimum of native libraries
- Can be downloaded from CVS and built from scratch in Eclipse
J2EE
J2EE profiling in TPTP is currently ramping a new resource. That person is gaining familarity with the codebase. We hope to document use cases here and solicit input in the future.
Our expectation from survey
If brief, we want to change profiler and support with feedback for product. :)
Getting started with TPTP
Information Sources
Stable TPTP usage scenarios
Profiling types
Performance issues which can be identified with TPTP
- Ineffective methods implementation
- Java memory leaks
- "static" specifier loss for data members
- Wrong tasks splitting for multithreading
Known TPTP profiler weaknesses
Some User Initial Experiences
As users come forward, we want to capture their initial experiences. We hope that some of these users will choose to become "lead user's" and migrate to the next section. :).
Profile on Server and Enabled mode Collection
A number of folks are trying to use TPTP to profile Tomcat and/or RCP applications and are launching/starting their app either from within the workbench or from a command line script. The summary of one user's initial experiences with the TPTP 4.4 profiler for a Tomcat based application are here
Using TPTP to profile JRE class libraries
JRE as all other application can have performance issues and hence area for its improvements. It consists from native and managed code, and portion of the last one is much bigger then often expected. So, for that portion we can use TPTP as profiler and localize with its help potential performance or resources usage issues. Also one of the goal is to estimate possibility of Java profiler usage for JRE profiling. Harmony is used as target JRE. For details watch page Harmony profiling with TPTP
Accepted lead user's projects
None, you have a chance :)
Contact points
Places where you can ask questions, discuss and of course proved feedback for the tool:
- TPTP Newsgroup
- TPTP Tracing&Profiling mailing list
- Contribution in Wiki
We get all information from these sources, analyse and put structured in Wiki. This is important for us and even small observation which published and discussed can affect overall quality and create product more attractive. So, please participate in community process and make TPTP better.