On Monday 10 January 2005 20:10, christof(_dot_)hoeke(_at_)e-7(_dot_)com wrote:
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?
Generic questions will typically give you generic answers;
You need to attack this in two initial steps, prior to worry about what to do
about it;
1. Solve the infrastructure, so that you can introduce special purpose code at
any point, without having to change everything in one go. Apache Cocoon or
something like it, could help you along this path. Cocoon operates with SAX
event pipe lines, and sounds like they are very suitable for you. Also,
Cocoon can often figure out what can be cached better than you can...
2. You need to measure the performance, in a way that is descriptive of what
the bottlenecks really are, so that you always can get a prioritized list of
what needs to be addressed. If you do 1. in a nice setup, you should be able
to collect and compile the performance figures using the same infrastructure.
Cheers
Niclas
--
---------------
Depression is merely anger without enthusiasm.
- Steven Wright
+---------//-------------------+
| http://www.dpml.net |
| http://niclas.hedhman.org |
+------//----------------------+
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--