Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hybrid TPTP scenario"
(→Most general case:) |
m (→Most general case:) |
||
| Line 16: | Line 16: | ||
====Most general case:==== | ====Most general case:==== | ||
# profile the squiggly browser when running the Tomcat 5.5 SVG jsp example | # profile the squiggly browser when running the Tomcat 5.5 SVG jsp example | ||
| − | ## experience | + | ## [[Profiling_Problems_in_4.4_Squiggly|experience]] |
# isolate the time spent in the batik code versus the browser code or on the network using the class/method statistics views in TPTP | # isolate the time spent in the batik code versus the browser code or on the network using the class/method statistics views in TPTP | ||
# profile the jsp on the tomcat server | # profile the jsp on the tomcat server | ||
Revision as of 20:18, 30 November 2007
Contents
TPTP Profiler users
- Harm Sluiman
Usage scenarios
Requirements and set up
To run this simple two tier application follow these steps:
- Install a default image of Tomcat 5.5 or newer
- Put your JRE 1.5 or newer on the path and run the tomcat5.exe in the tomcat bin directory
- open the tomcat welcome page or go to http://127.0.0.1:8080/ for a local install.
- login with the default userid and pwd
- run some of the sample applications to confirm things work, and then try the JSP SVG sample. This will give show tell you how to run the sample.
- download and unzip a recent batik binary driver from Apache
- with your JRE on the path run java -jar batik-squiggle.jar and enter the url provided when running the earlier jsp sample
You now have a running two tier java application. This is all free open source so easy to install and recreate as needed. You can try all this out on one machine but clearly the two processes will affect each other so using two machines for more formal measurement is better and creates the need for remote monitoring using the profiler.
Most general case:
- profile the squiggly browser when running the Tomcat 5.5 SVG jsp example
- isolate the time spent in the batik code versus the browser code or on the network using the class/method statistics views in TPTP
- profile the jsp on the tomcat server
- isolate the time spent in the jsp generated code and support libraries versus the tomcat server itself.
- compare these result to an end user clock
- optionally create a TPTP URL test for repeated testing of the server code without needing the browser
Required features:
- tbd
Ideal profiler
The ideal profiler will let me profile both of these applications at the same time or independently as well as show the network separations and impacts. At least one of these applications is normally on an separate machine so I would need remote support as well.
For the initial use case I only need to assess time spent, but it is important to note that I actually don't know the code I am profiling and am using the profiler to learn something about this code base before I write a line of code.
Opened Bugzillas
none yet