Preliminary results done in a controlled environment indicate that Saxon is
more scalable than Xalan. These tests were done under WSAD instead of WAS,
so they are preliminary; however, the difference in scalability can be seen
from the timings under load.
The testing tool used is the Microsoft Web Application Stress Tool, which is
free and works very well. The times given below are in milliseconds and
measure the average time to do an XSLT transformation to produce an HTML
table with 6 columns and 25 rows. The time is measured from the time of the
request until the last byte of HTML is received (TTLB). The XSLT is cached
as a Templates object using JAXP. The XML is also cached as a JAXP Source
object to eliminate this as a performance criteria.
15 Threads 25 Threads
Saxon Xalan Saxon Xalan
411 712 434 1183
To enable Saxon, use the following code before creating a
TransformerFactory:
System.setProperty("javax.xml.transform.TransformerFactory",
"com.icl.saxon.TransformerFactoryImpl");
Saxon version 6.5.3 was used for the test.
Stuart Zakon
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
manfred(_dot_)weigel(_at_)rzb(_dot_)at
Sent: Wednesday, January 28, 2004 11:25 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Antwort: RE: Antwort: [xsl] real XSLT performance
Hi,
We are running Cocoon2.1.3 (XML/XSLT Framework from apache) in WAS5 and had
to do some configuration tricks to improve the performance of the
transformations.
If your application is running inside a webcontainer you have two
possibilities:
1) Put your XSLT engine (I would recommand Saxon6.5.3 - the 7.x versions
won´t work with jdk .1.3.x) inside your WEB-INF/lib configure your app to
use this jar
if this is not possible
2) put the saxon jars in the classpath of your serverconfigfile, it will be
loaded on startup of your WAS test environment maybe your servlet needs an
init-param to look for it, but that depends on your app.
if you have any problems give me some details about your app / framework
regards
Manfred
stuart_zakon(_at_)medcohealth(_dot_)com@lists.mulberrytech.com am 28.01.2004
16:06:18
Bitte antworten an xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com@inet
Gesendet von: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
An: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Kopie:
Thema: RE: Antwort: [xsl] real XSLT performance
Manfred,
For now I could do the configuration in WSAD 5.1 if you give me a hint. That
will at least establish that XSLT <em>can</em> be done with some reasonable
performance in a WS environment. Then I can do the WAS configuration later.
Thanks for your help.
Stuart Zakon
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
manfred(_dot_)weigel(_at_)rzb(_dot_)at
Sent: Wednesday, January 28, 2004 3:09 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Antwort: [xsl] real XSLT performance
Hi Stuart,
The default xslt engine is a quiet old xalan version. When you ask for the
vendor (as Michael suggested) you will get Lotus Group Foundation.
This xslt processor is very slow!
Are you running your templates in a web container?
There are some tricky ways to tell websphere it should use another xslt
engine. Its easy to configure in WSAD but not that easy in your production
environment.
Which OS are you running (e.g. WAS on hostsystems is very different to the
AIX version) Are you using the WAS 5.1 EE?
regards
Manfred
stuart_zakon(_at_)medcohealth(_dot_)com@lists.mulberrytech.com am 27.01.2004
21:01:55
Bitte antworten an xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com@inet
Gesendet von: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
An: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Kopie:
Thema: [xsl] real XSLT performance
I am using JAXP Templates for performance and getting excellent results
under the Resin servlet engine. It is highly scalable with my stress tests
going from 5 to 100 concurrent threads with several steps in between.
However, when I move the test over to WebSphere 5.1 and WSAD 5.1, it doesn't
scale well beyond 5-10 concurrent threads. Which XSLT engine does WAS 5.1
use? Does anybody know of a high-performance XSLT engine for WebSphere?
Thanks,
S. Zakon
-----------------------------------------
This e-mail message and any attachments contain confidential information from
Medco Health Solutions, Inc. If you are not the intended recipient, you are
hereby notified that disclosure, printing, copying, distribution, or the taking
of any action in reliance on the contents of this electronic information is
strictly prohibited. If you have received this e-mail message in error, please
immediately notify the sender by reply message and then delete the electronic
message and any attachments.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list