Skip to main content

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.

Jump to: navigation, search

Hybrid TPTP scenario

Revision as of 19:51, 26 November 2007 by Sluiman.ca.ibm.com (Talk | contribs) (New page: ===TPTP Profiler users=== *Harm Sluiman ===Usage scenarios=== ====Most general case:==== # profile the squiggly browser when running the Tomcat 5.5 SVG jsp example # isolate the time spen...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

TPTP Profiler users

  • Harm Sluiman

Usage scenarios

Most general case:

  1. profile the squiggly browser when running the Tomcat 5.5 SVG jsp example
  2. isolate the time spent in the batik code versus the browser code or on the network
  3. profile the jsp on the tomcat server
  4. isolate the time spent in the jsp generated code and support libraries versus the tomcat server itself.
  5. compare these result to an end user clock
  6. optionally create a TPTP URL test for repeated testing of the server code without needing the browser

Required features:

  1. tbd

Ideal profiler

Ideal profiler

Opened Bugzillas

none yet

Back to the top