Hi Jacques,
Unfortunately this seems to be the number one complaint from our users. The TPTP team has made several attempts to address the scalability of our tools, but we simply haven't done an adequate job. It's really unfortunate to have all the functionality in TPTP and yet not meet the user requirements simply because of the fact that the tool is not scalable.
Having said that, there are still a few things you can do to speed up your profiling session.
1) If you're using IAC (i.e. Local Direct Connection), try using RAC 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
Due to the numerous complaints we've been getting about the performance of the profiler, I've opened an enhancement for a document that outlines suggestions (such as those listed above) on how you can speed up the profiler. Here's the enhancement: https://bugs.eclipse.org/bugs/show_bug.cgi?id=130133 . Feel free to add your email address to the CC list.
Thanks,
Navid Mehregani
| [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 02/03/2006 08:30 AM
|
|
I set up a tptp tracing and profiling tools environment into my eclipse system...
Windows 2000
Eclipse 3.1.2
Java 1.5.0_06
(cpu is Intel P4 1.5 Ghz / 768 Mb ram)
>From a pure functional point of view, it's all I ever dreamed of...
My sinceer kudos to those who developped that.
>From a pure practical point of view, it's not usable to profile a real-world application
for a very simple reason:
When profiled, the application's execution time is multiplied by a factor of 1000 (at least) !
(rough estimation after a balanced tree test)
I let you imagine my deception...
May be I did something wrong in the installation/configuration process ?
Or did I select the heaviest tracing options ?
Any idea/suggestion is welcome.
Friendly yours, Jacques_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
