Hi Jacques,
You can tune your profile by setting a more appropriate profiling set and profiling filter which target to your package/class/method, instead of getting almost everything in general. The default filter will only filter the most generic package, you should add your own filter entry to target your resources. Moreover, profile set is something you may want to consider.
Take a look at the following help regarding how to specify profiling criteria
http://help.eclipse.org/help31/index.jsp?topic=/org.eclipse.tptp.platform.doc.user/tasks/tefilter.htm
I can help you off the mailing list on setting a better filter and profiling set.
Regards.
------------------------------------------------------------------------------
Eugene Chan
IBM Toronto Laboratory, Canada
| [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 03/02/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
