This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Benchmarking Dynamic Web XSLT
- To: xsl-list at mulberrytech dot com
- Subject: Re: Benchmarking Dynamic Web XSLT
- From: Matt Sergeant <matt at sergeant dot org>
- Date: Tue, 18 Apr 2000 21:16:29 +0100 (BST)
- Reply-To: xsl-list at mulberrytech dot com
On Tue, 18 Apr 2000, Jon Smirl wrote:
> On a P2 350 Mhz, I'm able to do 10 gets/second. I use Apache JServ, XT and a
> database. The XSLT translation is not the problem. The overhead appears to
> be in the communication between apache, the app server and the database
> engine.
>
> 10 tps is 100ms per request with only about 12ms it in the XSLT engine (and
> it's written in Java). Cached, compiled XT is very fast.
How much does XT do on each request there? I'm assuming these fundamental
steps:
1. Parse source xml file into a tree structure
2. Determine template (from <?xml-stylesheet?> ??)
3. Parse template xml file into a tree structure
4. Perform XSLT transformations.
Basically you can skip 1, 3 and 4 given caching in the right places
(unless of course one of either the source or template changes) but I
don't know how far XT (and the other XSLT implementations) go on this.
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list