[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Stylesheet optimisation


Subject: RE: [xsl] Stylesheet optimisation
From: Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>
Date: Mon, 10 Jan 2005 10:37:36 -0600

Hi Chris,

> rendering performance of an XSLT set for a given project

Hm, I thought you were asking specifically for the rendering part of the web
pages - this however takes place in the browser. But does this really all
happen on the client browser?

> most steps use the same XML, only for some steps on selected pages a
different XML is used

This is an easy one. Simply put, caching your XSLT stylesheets should help
you gain a lot - but only if they won't change too much over time. And if
they do change, each and every stylesheet should also have its corresponding
cache invalidator. Doing this depends on the environment you use, but
there's no information on that.

If you need more specific information, let us know more details.

HTH,
<prs/>

-----Original Message-----
From: christof.hoeke@xxxxxxx [mailto:christof.hoeke@xxxxxxx] 
Sent: Lunes, 10 de Enero de 2005 06:11 a.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Stylesheet optimisation

Hi,
My question might be a bit too general, nevertheless: Are there any general
strategies/options to optimize the rendering performance of an XSLT set for
a given project?

A bit of background to the given project:
- a portal website with about 5000-10000 pages including dynamic pages
(applications and forms) which need to be rerendered with each request
- each page is rendered in about 3-5 different steps (due to the portal
software and/or pagetype)
- most steps use the same XML, only for some steps on selected pages a
different XML is used
- each step is rendered with its own XSLset, some are mostly the same and
included, some are completely different


Would there be any general optimisation options which could be applied to
the XSLT (not the general setup)? 
At the moment only caching of mostly static pages and prerendering of some
steps is done. Would something like custom XSLT extensions (for complex
stuff done now directly in XSL) be a help?

I know this *is* quite general, but any hints are very much appreciated...

Thanks
Chris


Current Thread
Keywords