This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XSLT and parallel processing
- To: <xsl-list at mulberrytech dot com>
- Subject: Re: XSLT and parallel processing
- From: "Tangi Vass" <tangivass at compuserve dot com>
- Date: Mon, 2 Oct 2000 12:14:36 +0200
- References: <200010011917.e91JHZw17070@sol.east.ora.com>
- Reply-To: xsl-list at mulberrytech dot com
For a web portal, I use pools of XT processors and Sun's parsers, each
instance running in a separate thread.
The most significant optimization has been achieved by subclassing
com.jclark.xsl.dom.XSLTransformEngine from XT to take benefit of a cache in
the getDocument() method.
I also interested in getting a parallized version of XT if someone has
worked on such a task :-)
Tangi Vass
----- Original Message -----
From: Erik Ray <eray@oreilly.com>
To: <xsl-list@mulberrytech.com>
Sent: Sunday, October 01, 2000 9:17 PM
Subject: XSLT and parallel processing
> The subtree processing model of XSLT seems to make it a good
> application for parallel processing (i.e. using multiple CPUs to
> process different subtrees simultaneously). Since many people have
> remarked on the inherent slowness of XSLT processors, I wonder if
> anyone has succeeded in creating an XSLT processor that successfully
> divides the work among different processors, resulting in a gain of
> processing speed. Has anyone tried this? Some of the implementations
> are written in Java, such as XT. Do they use multi-threading and can
> they take advantage of multiple CPUs?
>
>
> --
> Erik Ray
> O'Reilly and Associates
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list