Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » profile only parts of application
profile only parts of application [message #132014] Wed, 02 July 2008 17:30 Go to next message
Hauke Fuhrmann is currently offline Hauke FuhrmannFriend
Messages: 333
Registered: July 2009
Senior Member
Hi there,

I want to profile my own Eclipse plugin, i.e. the Eclipse application
with my plugin loaded.

The UML2 Class Interaction Sequence Diagrams just after startup really
becomes huge so even filters don't really help to navigate through it.

Is there any way to clear the data from the startup? I tried to select
the "Unload profiling data" context menu action. That empties the whole
data and the diagrams. But afterwards no new data gets recorded... Also
detaching from the agent and reattaching yields in empty data afterwards.

What to do?

Config:
Ganymede
Jdk 1.6.0
tptp tracing and profiling tools 4.3.100
internal linux agent controller

Hauke
Re: profile only parts of application [message #132635 is a reply to message #132014] Mon, 14 July 2008 07:41 Go to previous message
Asaf Yaffe is currently offline Asaf YaffeFriend
Messages: 333
Registered: July 2009
Senior Member
Hauke,

First, note that you should use TPTP 4.5 with Ganymede. I am not sure
whether TPTP 4.3 is fully supported on Ganymede.

With TPTP 4.5, you have multiple ways of profiling specific parts of
your application. Here's a summary:

1. Use filters. In the Monitor tab, you can configure the profiling
agent to collect data only for specific classes. The best approach for
profiling Eclipse plugins is to define a filter that INCLUDES all
classes from your plugin and EXCLUDE everything else.

2. Start profiling with data collection paused, and start data
collection when execution reaches an "interesting" point. To start with
data collection paused, double click the Profiling Agent in the monitor
tab and configure its behavior.

3. Start profiling, detach the profiler from the application, and then
reattach when execution reaches an "interesting" point. The
attach/detach operations are available by right-clicking the Profiling
Session node in the Profiling Monitor view.

4. Use the TPTP 4.5 new Profiler API feature. Please see the following
document for more information:
https://bugs.eclipse.org/bugs/attachment.cgi?id=87048

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Previous Topic:TPTP Profiling in Ganymede - only one option to profile?
Next Topic:Suggestions for behavior tab in testsuite
Goto Forum:
  


Current Time: Thu Sep 26 08:28:41 GMT 2024

Powered by FUDForum. Page generated in 0.26054 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top