Re: Saxon performance difference in eClipse and App S

Play the video

Subject: Re: Saxon performance difference in eClipse and App Server
From: Martin Honnen <Martin.Honnen@xxxxxx>
Date: Wed, 15 Dec 2010 18:08:18 +0100

Fraser Goffin wrote:

thanks for the advice. Moving away from using a DOMSource to a
StreamSource has cut the App Server times from 700-800ms to 150-180ms,
so that was really worthwhile.

I would now like to see if there is any further improvement possible
by using Saxon's native tree as per Micael's suggestion (a hint to get
me going would be helpful - do you mean using the S9 API (per the
examples you provide ?)

If you are using a StreamSource then I think Saxon will use that to build its native tree from it so there is nothing more you need to do to ensure that the native tree model is used instead of a DOM tree.

--

	Martin Honnen
	http://msmvps.com/blogs/martin_honnen/

Current Thread
Re: Saxon performance difference in eClipse and App Server Fraser Goffin - 15 Dec 2010 16:56:25 -0000 Michael Kay - 15 Dec 2010 17:20:11 -0000 Martin Honnen - 15 Dec 2010 17:29:37 -0000 <=

<- Previous	Index	Next ->
Re: Saxon performance differe, Michael Kay	Thread	Markers in tables and fo:retr, charlieo0
Re: Saxon performance differe, Michael Kay	Date	Markers in tables and fo:retr, charlieo0
	Month

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Subscribe in XML format

RSS 2.0
Atom 0.3

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >