This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
XSLT engine performance
- To: xsl-list at mulberrytech dot com
- Subject: XSLT engine performance
- From: Sebastian Rahtz <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Date: Wed, 26 Jul 2000 16:16:12 +0100 (BST)
- References: <00d401bff67e$09240150$876fbcd4@grig><1710.000726@iname.com>
- Reply-To: xsl-list at mulberrytech dot com
What is it with me and Oracle?
I just ran a test to see how different XSLT processors coped with
reading a 3mbyte XML file and going over the tree twice:
real user sys
XT: 0m23.131s 0m19.030s 0m0.510s
Saxon: 0m35.125s 0m28.900s 0m0.730s
Sablotron: 0m47.187s 0m39.320s 0m1.300s
Xalan: 0m55.277s 0m50.540s 0m1.280s
Oracle: 6m56.811s 1m15.790s 0m10.920s
the interesting results here are
- Oracle has some real problem in working well for me :-}
- Sablotron is slower than Saxon, despite being compiled C++
bizarrely, Xalan produced the results even though it (rightly) said my
XML file was not valid against the DTD. Is this to be expected?
does anyone have reason to doubt the above ranking, apart from the odd
Oracle result?
Sebastian Rahtz
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list