OK, for 3Gb you need to look at the other options such as streaming transformations or document projection. Note, both these are Saxon-SA options. (Or you could do your own preprocessing with a SAX filter, etc.)
Michael Kay

From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Julio de la Vega
Sent: 17 December 2007 11:02
To: Mailing list for SAXON XSLT queries
Subject: Re: [saxon] Question about XSLT >> Huge Files

Thank you for your answers.


Increasing the amount of memory available to the JVM using the xmx was the first step we did but it is no enough for the size of our files. At the moment my input xml files are more or less 3 Gb but they will be bigger in the future.


In my first tests with files about 500 Mb, the amount of memory in use increased to big values so it was impossible to do the XSLT transformation because of java heap errors.

2007/12/17, Andrew Welch <andrew.j.welch@gmail.com>:
On 17/12/2007, Julio de la Vega <juvepo@gmail.com> wrote:
> I am working in a case where I have to transform an XML input in a more
> complex XML output. I have developed an XSLT that creates my XML output
> according to my requirements. My problems have started when I have begun to
> run huge xml input files because of problems of memory.

> Could you please give me an overview about how could I solve this case?

Increase the amount of memory available to the JVM using the xmx switch, eg:

java -Xmx1024M ........

Andrew Welch
Kernow: http://kernowforsaxon.sf.net/

SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
saxon-help mailing list