Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » Slow profiling of Java application

Show: Today's Messages :: Show Polls :: Message Navigator

Slow profiling of Java application [message #72046]

Mon, 29 May 2006 08:53

Eclipse User

Originally posted by: eygelaar.sun.ac.za

Hi,

I am busy developing a Java application for my MScEng thesis. Solving a
simple problem without the profiler takes about +/- 1 or 2 seconds. But,
profiling the application takes a really long time. After 5 minutes I stop
the profiler. I am puzzled why profiling the application takes such a long
time.

I am using the standard "Execution History - Statistical" profiling set,
Eclipse 3.1.2, TPTP 4.1.0.1, ThinkPad T42, 1gig RAM.

Any help will be welcome.

Thanks,
Anton

Report message to a moderator

Re: Slow profiling of Java application [message #72255 is a reply to message #72046]

Tue, 30 May 2006 14:28

Eclipse User

Originally posted by: nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 004F813E8525717E_=
Content-Type: text/plain; charset="US-ASCII"

Here are some suggestions on how you can speed up the profiler:

1) If you're using IAC (i.e. Local Direct Connection), try using the Agent
Controller instead
2) Selecting fewer profiling options will make things faster. Try
avoiding the graphical details option and the collection of instance level
information if possible.
3) The most important thing is to make sure you have your filters set up
properly. In your launch configuration -> click on 'Profiling' -> Select
your profiling set -> 'Edit' -> 'Next' -> 'Next' -> Set your filter set.
Try to exclude everything you're not interested in. This is the filterset
I usually use:
Class Method Mode
org.mypackage* * INCLUDE <--
Include everything in my package
* *
EXCLUDE <-- Exclude everything else

4) If it's still too slow, try profiling to a file: -> in the 'Profiling'
tab of your launch configuration -> click on the 'Destination' tab ->
'Send profiling data to a file'. You can later import the profiling file
by going to File -> Import

Navid Mehregani
--=_alternative 004F813E8525717E_=
Content-Type: text/html; charset="US-ASCII"

 Here are some suggestions on how you
can speed up the profiler:
 
 1) If you're using IAC (i.e. Local Direct
Connection), try using the Agent Controller instead
 
2) Selecting fewer profiling options will make things faster.  Try
avoiding the graphical details option and the collection of instance level
information if possible. 
3) The most important thing is to make sure you have your filters set up
properly.  In your launch configuration -> click on 'Profiling'
-> Select your profiling set -> 'Edit' -> 'Next' -> 'Next'
-> Set your filter set.  Try to exclude everything you're not interested
in. This is the
filterset I usually use: 
Class                    
               Method    
         Mode 
org.mypackage*                
  *                  
  INCLUDE      <--  Include everything in my
package 
*                    
                     
        *            
        EXCLUDE     <-- Exclude everything
else 
 
4) If it's still too slow, try profiling to a file: -> in the 'Profiling'
tab of your launch configuration -> click on the 'Destination' tab ->
'Send profiling data to a file'.  You can later import the profiling
 file by going to File -> Import 
 
 Navid Mehregani
--=_alternative 004F813E8525717E_=--

Report message to a moderator

Previous Topic:	Error into Sample Birt Report
Next Topic:	The Open Group Application Response Measurement

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 10:20:18 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter