Thank you so much for your kind response; your explanation is helpful for sure. I still have some questions; (1) how could I save the execution flow as .XML file like we did about the call graph in execution statistics; the "SAVE." option in "Profiling Monitor" saves the profiles as .TRCPXMI file; but I don't know how to open and reuse it; I try to use the "New Report" to save the execution flow as .XML file, but it looks like only execution statistics is included, no information about the execution flows. (2) Setting filter includes the Class/method(s) I am interested in. Is there any way to included only the Class/methods I wrote, but exclude all the others. I use following settings in monitor: include * methods in MyPackageName.*, but exclude * methods in Java*, com.ibm* and etc. However, it doesn't work. I wonder if you can help me to figure out these problems; thanks a lot;
________________________________ From: Mike Reid <miker...@ca.ibm.com> To: TPTP Tracing and Profiling Tools Project developer discussions <tptp-tracing-profiling-tools-dev@eclipse.org> Sent: Wed, January 12, 2011 5:53:26 PM Subject: Re: [tptp-tracing-profiling-tools-dev] Two simple questions about the TPTP; thanks a lot! Hi Sd, > I am a newer of TPTP; I have two simple questions about this tool: > (1): how could I save the execution flow as we did about the call graph; Any profiling data collected by the workbench can be saved by right-clicking the desired resource in the "Profiling Monitor" and selecting "Save". Additionally, you will be prompted to save any unsaved data when you exit the workbench. Perhaps I'm not entirely understanding your question? > (2): when I follow the tutorial provided in > http://www.eclipse.org/articles/Article-TPTP-Profiling-Tool/ > tptpProfilingArticle.html > (all settings are by default) the results(call graph) never > show the information about "parser.parse(is, this)"; > When calling parse(...), it calls "startDocument" , > "startElements" and etc instead; but I still wonder if the TPTP can > display these information (the call graph of parse(...)) any way; I haven't reviewed the code attached the article, but if you're not seeing the data you want in the profiling views the first thing to check would be that the filter set includes the Class/method(s) you are interested in. The article seems to only include classes in the com.sample.product* package (step 3b), if the parse() method you're interested in doesn't live in that package you'll have to expand the filter set appropriately to get any data on it. Does that help? Mike Reid Test and Performance Tools Rational Application Developer for WebSphere phone. 905-413-2282 | fax. 905-413-4850 e-mail. miker...@ca.ibm.com
_______________________________________________ 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
