Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » TPTP Profiler GUI component re-use
TPTP Profiler GUI component re-use [message #122105] Tue, 05 February 2008 01:01 Go to next message
Eclipse User
Originally posted by: ck2329.mail.ru

I investigated TPTP profiler for last 2 weeks and unfortunately found set
of weak points :

* Complicated "on-target" part - for TPTP profiler usage both Agent
Controller and JVMTI agent must be ported to the target system (mine is
not Intel x86 )
* XML transport - great overhead on hard profiling tasks
* NO way for simultaneous use of different profiling views (memory &
threads for example)

BUT! As my engineers are using Eclipse for most of dev tasks - they wants
to stay on Eclipse platform.
So my question - Is it possible to rewrite backend part and keep frontend
(Eclipse GUI components)? Is there any intermediate layer between Eclipse
GUI ccomponents and profiler logic layer ?

My wish is to keep only small JVMTI agent on target site - this agent must
only know how to filter messages, do instrumentation and pass data to
sockets.

Probably it is possible to combine TPTP GUI with NetBeans Profiler agent ?
:-)
Any suggestions ?

Report message to a moderator

Re: TPTP Profiler GUI component re-use [message #123313 is a reply to message #122105] Mon, 18 February 2008 02:26 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Andrew,

> So my question - Is it possible to rewrite backend part and keep
> frontend (Eclipse GUI components)? Is there any intermediate layer
> between Eclipse GUI ccomponents and profiler logic layer ?

The TPTP Profiler back-end and front-end components are completely
separated. The only thing that "glues" them together is the ability of
the front-end to import data generated by the back-end. For offline
profiling scenarios (assuming you do not want to port the Agent
Controller to your target platforms), all you need to do is develop a
profiling (e.g. JVMTI) agent that produces output file in a format
supported by the front-end. You can then import this file into the
workbench for analysis.

Currently, the TPTP profiler backend generates output in a format called
XML4Profiling, which is described here:
http://www.eclipse.org/tptp/platform/documents/resources/pro filingspec/XML4Profiling.htm

For TPTP 4.5, we are currently working on a replacement binary format.
This work is described here: https://bugs.eclipse.org/196713. Please see
dependent bugs 209342 and 209343 for the back-end (profiler) and
front-end (Eclipse Workbench) specific details and patches.

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler

Report message to a moderator

Re: TPTP Profiler GUI component re-use [message #123364 is a reply to message #123313] Tue, 19 February 2008 02:43 Go to previous messageGo to next message
Eclipse User
Originally posted by: ck2329.mail.ru

Thanks for reply, Asaf.

Actually xml4profiling - is the bottle neck we need to avoid.

But to be clear - we need online profiling exactly. Idea is to remove AC
and make agent as simple as possible - agent should just catch events, do
instrumentation and send data via tcp/ip.

Actully now im trying to bring current tptp version to work with our
specific platform and os.

One more Q: you said that front-end just imports profiling data from
back-end - so when you say 'import' - is it online(continious) import or
offline(just once) import/

Report message to a moderator

Re: TPTP Profiler GUI component re-use [message #123389 is a reply to message #123364] Tue, 19 February 2008 06:47 Go to previous message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Andrew V. Novoselsky wrote:
> One more Q: you said that front-end just imports profiling data from
> back-end - so when you say 'import' - is it online(continious) import or
> offline(just once) import/

It depends on the usage scenario. With "online profiling" (using the
Agent Controller), the AC sends data via tcp/ip to the workbench, and
there is some "AC Client Side" code that receives this data and writes
it into the data model. The write happens each time the client receives
data from the Agent Controller.

With "offline" profiling, the entire file is imported in "one shot" into
the workbench.

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler

Report message to a moderator

Previous Topic:Can't Get Profiler to Run
Next Topic:Integrated agent controller does not work: launching eclipse hangs
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat May 18 02:00:00 EDT 2013

Powered by FUDForum. Page generated in 0.05227 seconds