saxon:next-in-chain and memory usage

Play the video

Subject: saxon:next-in-chain and memory usage
From: "Frederik Fouvry frederik.fouvry@xxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 9 Nov 2016 12:56:57 -0000

Hello,

I am running a pipeline of XML transformations over an XML file of about 130Mb, using Saxon 9.1.0.5J and Java 1.8.0_112. The pipeline is implemented using saxon:next-in-chain. It works fine as long as I have fewer than about five steps, but when I have five or more, then Java runs out of memory, regardless of the complexity of the style sheets (as the simplest, I tried the identity transformation). Is this to be expected? Is the result of each step kept in memory? Or is it due to something else?

Giving Java more memory seems to help in some cases, but because the size of the file can vary a lot (mostly it will be smaller, but in some cases, it may be bigger), that is not a scalable solution.

Many thanks,

Frederik Fouvry

Current Thread
saxon:next-in-chain and memory usage Frederik Fouvry frederik.fouvry@xxxxxxxxxxxx - 9 Nov 2016 15:14:48 -0000 <= Michael Kay mike@xxxxxxxxxxxx - 9 Nov 2016 15:14:48 -0000 Frederik Fouvry frederik.fouvry@xxxxxxxxxxxx - 9 Nov 2016 17:19:33 -0000

<- Previous	Index	Next ->
Re: XSLT 2: Best Way to Synth, Dimitre Novatchev dn	Thread	Re: saxon:next-in-chain and m, Michael Kay mike@xxx
Re: XSLT 2: Best Way to Synth, Dimitre Novatchev dn	Date	Re: saxon:next-in-chain and m, Michael Kay mike@xxx
	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 >