|Profiling workaround [message #128555]
||Thu, 17 April 2008 16:32
| Joerg Bullmann
Registered: July 2009
Have not solved my problem of before, but have finally settled on a |
workaround: I start my application and have the profiling data dumped to a
file. Then -- after the app has finished -- I manually import that
information and inspect it with TPTP's viewers.
Here's how I have set up my run config to gather the data:
Add this as a VM argument in the run configuration's "Arguments" tab:
Add the following three definitions in the run configuration's
JAVA_PROFILER_HOME = C:\Program Files\TPTP Agent
PATH = C:\Program Files\TPTP Agent
TPTP_AC_HOME = C:\Program Files\TPTP Agent Controller
When running this configuration, it will leave a heap profile log file in
C:\data\TPVF\prof.trcxml which can imported in Eclipse using
"Import>Profiling and Logging>Profiling file".
Background about the above info can be found in
plugins\org.eclipse.tptp.javaprofiler\readme.txt in the TPTP agent
Hope this helps. I still hope profiling will eventually start working
properly right from the IDE.
I'd appreciate feedback whether this workaround helps people and in which
way it can be improved.
Powered by FUDForum
. Page generated in 0.01746 seconds