Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 108890 - Develop an Aggregating Agent for execution trace
Summary: Develop an Aggregating Agent for execution trace
Status: CLOSED DUPLICATE of bug 108646
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement with 8 votes (vote)
Target Milestone: ---   Edit
Assignee: Bob Duncan CLA
QA Contact:
URL: http://www.eclipse.org/tptp/groups/Ar...
Whiteboard: closed460
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 20:16 EDT by Anandi Krishnamurthy CLA
Modified: 2016-05-05 11:20 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anandi Krishnamurthy CLA 2005-09-06 20:16:23 EDT
The performance and scalability of TPTP execution trace is very poor.
The user is at the mercy of setting narrow filters to get data.

An agent that aggregates trace data will perform and scale better.
There are a couple of major ways of doing this: JVMPI based versus 
Byte Code Insertion based, each with its own pros and cons.

Review the options and generate a plan for adding this capability.
Comment 1 Christophe Telep CLA 2005-09-15 12:06:16 EDT
Change Version to 4.2 to be reviewed by requirement group for 4.2 planning
Comment 2 Sri Doddapaneni CLA 2005-09-15 15:09:24 EDT
Changing the component to Trace.JVMTI.
If this is also a requirement on JVMPI agent, we need another entry to track 
it.
Comment 3 Sri Doddapaneni CLA 2005-09-15 17:01:48 EDT
This is a request for JVMPI agent according to Allan Pratt.
Comment 4 Bob Duncan CLA 2005-12-08 23:39:45 EST

*** This bug has been marked as a duplicate of 108646 ***
Comment 5 Paul Slauenwhite CLA 2009-06-30 06:24:42 EDT
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. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
Comment 6 Paul Slauenwhite CLA 2009-06-30 13:29:14 EDT
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.