This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Re: XSLT and parallel processing (Was: RE: XSL-List Digest V3 #1125)
- To: <xsl-list at lists dot mulberrytech dot com>, <AdamsC at kssg dot com>
- Subject: RE: [xsl] Re: XSLT and parallel processing (Was: RE: XSL-List Digest V3 #1125)
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Thu, 27 Sep 2001 14:46:10 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
> The modification that has to be done does not seem too complex:
>
> For every member of a sequence S of (sibling)
> content-producing xsl instructions
> (e.g. xsl:apply-templates) initiate its execution in a
> separate thread. When all
> threads have completed, serialize their outputs based on
> their code position in the sequence S.
>
I think if you did that, the synchronization overhead would certainly be too
high. You'd be starting a thread to process each node in the source tree.
The general approach is sound, but it needs to be applied more
discriminatingly.
Also, it doesn't tackle the challenge of doing the transformation in
parallel with the parsing, tree building, and serialization.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list