Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » execution time analysis for eclipse workbench
execution time analysis for eclipse workbench [message #83248] Tue, 12 September 2006 19:04 Go to next message
Eclipse UserFriend
Originally posted by: aasingh.cs.ubc.ca

Hi,

I tried to profile an instance of eclipse by selecting Run > Profile
...., then creating a new eclipse application configuration, then
clicking on the monitor tab and checking the execution time analysis
checkbox. The new instance of eclipse starts up. When I right click on
"Execution Time Analysis" in the Profiling Monitor view and select "Open
With > Execution Statistics"), The execution Statistics view comes up
but informs me that "No execution statistics is available for display.
Either you have no trace selected in the Profiling Monitor view or the
current selection does not contain execution statistic information." I
installed the Agent Controller and it is running. Does anybody know
what I am doing wrong?

Thanks,
Arjun
Re: execution time analysis for eclipse workbench [message #83266 is a reply to message #83248] Tue, 12 September 2006 20:40 Go to previous messageGo to next message
Randy D. Smith is currently offline Randy D. SmithFriend
Messages: 394
Registered: July 2009
Senior Member
Arjun Singh wrote:
> Hi,
>
> I tried to profile an instance of eclipse by selecting Run > Profile
> ..., then creating a new eclipse application configuration, then
> clicking on the monitor tab and checking the execution time analysis
> checkbox. The new instance of eclipse starts up. When I right click on
> "Execution Time Analysis" in the Profiling Monitor view and select "Open
> With > Execution Statistics"), The execution Statistics view comes up
> but informs me that "No execution statistics is available for display.
> Either you have no trace selected in the Profiling Monitor view or the
> current selection does not contain execution statistic information." I
> installed the Agent Controller and it is running. Does anybody know
> what I am doing wrong?
>
> Thanks,
> Arjun

With what you're giving me, I can't definitively say what you're doing
wrong... or even if you're doing anything wrong at all. Mostly I can
just tell you problems we've seen others run into. I'll assume you're
running Eclipse TPTP 4.2 on Eclipse 3.2 (or some subsequent variation of
either).

First, are we dealing with Windows or Linux? If Linux, sometimes it is
the failure to specify the LD_LIBRARY_PATH prior to starting the agent
controller.

Second, are we dealing with a potential 32-/64-bit situation here? We've
seen people have the JVM fail to find the piAgent dynamic link library
(the thing that attaches to the JVM to do the actual profiling data
collection) because the piAgent did not "match" the chosen JVM ... so if
you're on a 64-bit architecture... this could be the problem.

Third... you "installed the Agent Controller and it is running" ... but
was it running prior to the start of the original Eclipse workbench? If
so... you should be working with that AC; if not, you're really going
through the IAC (internal/integrated agent controller) and the AC is
really irrelevant.

Give me as much specific info you can (which JVM, what versions of
everything, etc) and I'll try to help further.
--
RDS

Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
Re: execution time analysis for eclipse workbench [message #83304 is a reply to message #83266] Tue, 12 September 2006 21:13 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: aasingh.cs.ubc.ca

Sorry for not being specific enough. I'm using Eclipse 3.2 and TPTP
4.2, Agent Controller 4.2, and Java 1.5. I'm running Windows XP on a 32
bit machine. I've tried running the agent controller both ways (running
ACServer.exe, and using managedservice.exe and starting the windows
service) prior to launching eclipse.

I should mention that I am able to see execution time analysis when
launching a local Java application (Run > Profile... then selecting a
configuration for a Java Application that is in my workspace). So this
problem seems to arise only when dealing with Eclipse Application
configurations.

Thanks,
Arjun

Randy D. Smith wrote:
> Arjun Singh wrote:
>> Hi,
>>
>> I tried to profile an instance of eclipse by selecting Run > Profile
>> ..., then creating a new eclipse application configuration, then
>> clicking on the monitor tab and checking the execution time analysis
>> checkbox. The new instance of eclipse starts up. When I right click
>> on "Execution Time Analysis" in the Profiling Monitor view and select
>> "Open With > Execution Statistics"), The execution Statistics view
>> comes up but informs me that "No execution statistics is available for
>> display. Either you have no trace selected in the Profiling Monitor
>> view or the current selection does not contain execution statistic
>> information." I installed the Agent Controller and it is running.
>> Does anybody know what I am doing wrong?
>>
>> Thanks,
>> Arjun
>
> With what you're giving me, I can't definitively say what you're doing
> wrong... or even if you're doing anything wrong at all. Mostly I can
> just tell you problems we've seen others run into. I'll assume you're
> running Eclipse TPTP 4.2 on Eclipse 3.2 (or some subsequent variation of
> either).
>
> First, are we dealing with Windows or Linux? If Linux, sometimes it is
> the failure to specify the LD_LIBRARY_PATH prior to starting the agent
> controller.
>
> Second, are we dealing with a potential 32-/64-bit situation here? We've
> seen people have the JVM fail to find the piAgent dynamic link library
> (the thing that attaches to the JVM to do the actual profiling data
> collection) because the piAgent did not "match" the chosen JVM ... so if
> you're on a 64-bit architecture... this could be the problem.
>
> Third... you "installed the Agent Controller and it is running" ... but
> was it running prior to the start of the original Eclipse workbench? If
> so... you should be working with that AC; if not, you're really going
> through the IAC (internal/integrated agent controller) and the AC is
> really irrelevant.
>
> Give me as much specific info you can (which JVM, what versions of
> everything, etc) and I'll try to help further.
Re: execution time analysis for eclipse workbench [message #83422 is a reply to message #83304] Wed, 13 September 2006 00:53 Go to previous message
Eclipse UserFriend
Originally posted by: aasingh.cs.ubc.ca

Looks like I found out what the problem was. There was no execution
time analysis because the default filter excludes all packages beginning
with org, which is what just about all of the eclipse plugins start
with. Once I changed the filter to include packages beginning with org,
I was able to see the execution time analysis for the packages from the
Eclipse plugins, which is exactly what I wanted.

Arjun

Arjun Singh wrote:
> Sorry for not being specific enough. I'm using Eclipse 3.2 and TPTP
> 4.2, Agent Controller 4.2, and Java 1.5. I'm running Windows XP on a 32
> bit machine. I've tried running the agent controller both ways (running
> ACServer.exe, and using managedservice.exe and starting the windows
> service) prior to launching eclipse.
>
> I should mention that I am able to see execution time analysis when
> launching a local Java application (Run > Profile... then selecting a
> configuration for a Java Application that is in my workspace). So this
> problem seems to arise only when dealing with Eclipse Application
> configurations.
>
> Thanks,
> Arjun
>
> Randy D. Smith wrote:
>> Arjun Singh wrote:
>>> Hi,
>>>
>>> I tried to profile an instance of eclipse by selecting Run > Profile
>>> ..., then creating a new eclipse application configuration, then
>>> clicking on the monitor tab and checking the execution time analysis
>>> checkbox. The new instance of eclipse starts up. When I right click
>>> on "Execution Time Analysis" in the Profiling Monitor view and select
>>> "Open With > Execution Statistics"), The execution Statistics view
>>> comes up but informs me that "No execution statistics is available
>>> for display. Either you have no trace selected in the Profiling
>>> Monitor view or the current selection does not contain execution
>>> statistic information." I installed the Agent Controller and it is
>>> running. Does anybody know what I am doing wrong?
>>>
>>> Thanks,
>>> Arjun
>>
>> With what you're giving me, I can't definitively say what you're doing
>> wrong... or even if you're doing anything wrong at all. Mostly I can
>> just tell you problems we've seen others run into. I'll assume you're
>> running Eclipse TPTP 4.2 on Eclipse 3.2 (or some subsequent variation
>> of either).
>>
>> First, are we dealing with Windows or Linux? If Linux, sometimes it is
>> the failure to specify the LD_LIBRARY_PATH prior to starting the agent
>> controller.
>>
>> Second, are we dealing with a potential 32-/64-bit situation here?
>> We've seen people have the JVM fail to find the piAgent dynamic link
>> library (the thing that attaches to the JVM to do the actual profiling
>> data collection) because the piAgent did not "match" the chosen JVM
>> ... so if you're on a 64-bit architecture... this could be the problem.
>>
>> Third... you "installed the Agent Controller and it is running" ...
>> but was it running prior to the start of the original Eclipse
>> workbench? If so... you should be working with that AC; if not, you're
>> really going through the IAC (internal/integrated agent controller)
>> and the AC is really irrelevant.
>>
>> Give me as much specific info you can (which JVM, what versions of
>> everything, etc) and I'll try to help further.
Previous Topic:Identifying Executed Lines of Code Using ProbeKit (2)
Next Topic:Perfmon problem
Goto Forum:
  


Current Time: Sat Apr 20 02:10:40 GMT 2024

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

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

Back to the top