TPTP Profiler GUI component re-use [message #122105] |
Tue, 05 February 2008 06:01 |
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 ?
|
|
|
|
Re: TPTP Profiler GUI component re-use [message #123364 is a reply to message #123313] |
Tue, 19 February 2008 07:43 |
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/
|
|
|
|
Powered by
FUDForum. Page generated in 0.04053 seconds