[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: saxon:next-in-chain and memory usage
Thanks for the pointer. Unfortunately, it looks like we'll have to take
a very different route: the XProc processors I've looked at (Calabash,
MorganaXProc) run into the same problem.
FWIW: I'm now trying (with XSLT 2.0) to use a combination of xsl:result-document and saxon:next-in-chain to split the input file (it consists of relatively small-sized chunks; the big size of the original file is mainly due to the large number of chunks), and process each of the chunks separately, and then merge again them in the last step. I have a prototype that looks promising. (I'll need to deal with any cross-references later on, but I'm fairly confident that this will work too. And I'll have to get rid of the temporary files ...) Thanks, Frederik Fouvry On 09.11.2016 14:01, Michael Kay mike@xxxxxxxxxxxx wrote: I remember at some stage doing some work to ensure that saxon:next-in-chain released memory from one stylesheet before running the next, but I haven't checked that this is the case today, and there have been considerable changes in the way it's implemented. And in any case 9.1 is a pretty old release. I would encourage you to use a different pipelining technology, for example XProc.
|
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
|