Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TPTP-AG-20080219"
(New page: == Date == * February 19, 2008 == Attendees == * Present: * Paul Slauenwhite * Asaf Yaffe * Alexander Alexeev * Chris Elford * Mikhail Loenko * Vasily Levchenko * Joe Toomey == Topic ...) |
|||
| (10 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
* Present: | * Present: | ||
| − | + | ** Paul Slauenwhite | |
| − | * Paul Slauenwhite | + | ** Asaf Yaffe |
| − | * Asaf Yaffe | + | ** Eugene Chan |
| − | * Alexander Alexeev | + | ** Alexander Alexeev |
| − | * | + | ** Joanna Kubasta |
| − | * | + | ** Chris Elford |
| − | * | + | |
| − | * | + | |
== Topic == | == Topic == | ||
| − | * Alex A. will host a technical discussion on enhancement 200320 ( | + | * Alex A. will host a technical discussion on enhancement [https://bugs.eclipse.org/bugs/show_bug.cgi?id=200320 200320 ((ThreadProf) Add contention analysis features to TPTP Profiler)], focusing on the design and implementation of the enhancement. |
* [http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_200320.html Updated Description Document] | * [http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_200320.html Updated Description Document] | ||
| Line 23: | Line 21: | ||
== Minutes == | == Minutes == | ||
| − | * | + | * Background on the Thread Profiler: |
| + | ** Martini/JVMTI agent. | ||
| + | ** Trace model extensions (e.g. thread start/stop and thread states). | ||
| + | ** Two profiler views (Thread Statistics and Thread Utilization views). | ||
| + | |||
| + | * Contention analysis: | ||
| + | ** Monitor contention: | ||
| + | *** Locates monitor requests while other threads own it. | ||
| + | *** Leads to deadlock. | ||
| + | ** Data Contention: | ||
| + | *** Locates data requests while other threads are using it. | ||
| + | *** Leads to data corruption. | ||
| + | |||
| + | * Proposed UI changes: | ||
| + | *** New Data Contention view. | ||
| + | *** Updates to the Thread Utilization view such as filter sets and interactions between threads. | ||
| + | *** Critical path analysis: | ||
| + | **** Determines which activities are critical and shortening the path by adding resources and performance tuning: | ||
| + | |||
| + | [[Image:image002.jpg]] | ||
| + | |||
| + | * Proposed thread events: | ||
| + | ** Changes to the model loader to handle the following new events: | ||
| + | |||
| + | [[Image:image016.gif]] | ||
| + | |||
| + | * Proposed Trace model changes: | ||
| + | ** Joint thread execution and their interaction including thread start/stop and thread states based on the proposed thread events. | ||
== Questions/Answers == | == Questions/Answers == | ||
| − | * '''Q:''' | + | * '''Q:''' Will the existing UML2 thread sequence diagram support the new thread information added to the model under this defect? |
| − | * '''A:''' | + | * '''A:''' This will not be included in the scope of this enhancement. Eugene opened dependent enhancement [https://bugs.eclipse.org/bugs/show_bug.cgi?id=219442 219442] to track this work item. |
| − | * '''Q:''' | + | * '''Q:''' Is the contention analysis instrumentation going to be done at class load time or attach time? |
| − | * '''A:''' | + | * '''A:''' Both are supported and the preference is configured in the UI. |
| − | * '''Q:''' | + | * '''Q:''' Why are some of the thread event attributes implied? |
| − | * '''A:''' | + | * '''A:''' The [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.dtd.html DTD] for the [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/XML4Profiling.htm Event Specification for Java profiling] on the Platform Project [http://www.eclipse.org/tptp/platform/documents/index.php web site] was used and may not be correct. The [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/XML4Profiling.htm Event Specification for Java profiling], [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.dtd.html DTD], and [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.xsd XSD] should be updated with these new thread events. |
== Action Items == | == Action Items == | ||
| − | * | + | * Alex A. to update the [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/XML4Profiling.htm Event Specification for Java profiling], [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.dtd.html DTD], and [http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.xsd XSD] with these new thread events. |
| + | |||
| + | * Alex A. to reply to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=200320#c7 Paul's comments]. | ||
Latest revision as of 10:06, 29 February 2008
Date
- February 19, 2008
Attendees
- Present:
- Paul Slauenwhite
- Asaf Yaffe
- Eugene Chan
- Alexander Alexeev
- Joanna Kubasta
- Chris Elford
Topic
- Alex A. will host a technical discussion on enhancement 200320 ((ThreadProf) Add contention analysis features to TPTP Profiler), focusing on the design and implementation of the enhancement.
Minutes
- Background on the Thread Profiler:
- Martini/JVMTI agent.
- Trace model extensions (e.g. thread start/stop and thread states).
- Two profiler views (Thread Statistics and Thread Utilization views).
- Contention analysis:
- Monitor contention:
- Locates monitor requests while other threads own it.
- Leads to deadlock.
- Data Contention:
- Locates data requests while other threads are using it.
- Leads to data corruption.
- Monitor contention:
- Proposed UI changes:
- New Data Contention view.
- Updates to the Thread Utilization view such as filter sets and interactions between threads.
- Critical path analysis:
- Determines which activities are critical and shortening the path by adding resources and performance tuning:
- Proposed thread events:
- Changes to the model loader to handle the following new events:
- Proposed Trace model changes:
- Joint thread execution and their interaction including thread start/stop and thread states based on the proposed thread events.
Questions/Answers
- Q: Will the existing UML2 thread sequence diagram support the new thread information added to the model under this defect?
- A: This will not be included in the scope of this enhancement. Eugene opened dependent enhancement 219442 to track this work item.
- Q: Is the contention analysis instrumentation going to be done at class load time or attach time?
- A: Both are supported and the preference is configured in the UI.
- Q: Why are some of the thread event attributes implied?
- A: The DTD for the Event Specification for Java profiling on the Platform Project web site was used and may not be correct. The Event Specification for Java profiling, DTD, and XSD should be updated with these new thread events.
Action Items
- Alex A. to update the Event Specification for Java profiling, DTD, and XSD with these new thread events.
- Alex A. to reply to Paul's comments.