This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Benchmarking Dynamic Web XSLT
> My db integration phase does not produce XML directly, it fires SAX events
> instead.
My PXSLServlet ( www.pault.com ) does it exactly the same way.
SQL query get's executed e t.c. and finaly XT receives the stream
of appropriate SAX events.
> This avoids parsing at one stage. I have a layer that sits between
> the db integration code and XT that scans the SAX events looking for
> <?xml-stylesheet>.
I have the name of the stylesheet provided as a parameter
of HTTP request.
> When it sees the style sheet directive I take the cached
> XSLT sheet from XT and clone it.
Before dong this I'm checking the timestamp of the file which contains
the stylesheet. If it has changed - I'm reloading the stylesheet, if not -
stylesheet is cloned from the cached copy. That's only to allow debuging
of the stylesheet without restarting the servlet engine.
> Then I fire SAX events into it representing my input XML.
So do I.
> Performance of the transformation is not the problem.
... if the transformation is simple and because you are sorting your data
on the level of the database, grouping your data on the level of database
and filtering your data on the level of database ( like PXSLServlet does ), your
transformations *are* simple.
Right ?
> The problem is all of the socket overhead and process switching.
> I'm reworking my system right now to use Tomcat in webserver mode,
> my app server and Hypersonic db all in a single task. I'm expecting it to be
> much faster.
I have tried PXSLServlet with Sun's JSDK 2.1. JSDK 2.1 contains the
servlet-runner which is in fact not a servlet-runner, but web-server with
builtin servlet engine written in java and I'm happy with it. It looks robust
and works efficienly even on a crappy hardware. It is interesting to
compare the efficiency of JSDK 2.1 ( all-in-one) with Apache / Jrun / Tomcat.
Rgds.Paul.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list