Emmanuel,

It looks like a perfect XProc usecase

Xmlizer

2012/10/16 Emmanuel Bégué <eb@medusis.fr>
On Sat, Oct 13, 2012 at 5:40 PM, Michael Kay <mike@saxonica.com> wrote:
> Apart from anything else, using next-in-chain is heavy on memory usage
> because when each transformation is invoked from the previous one, the
> previous one doesn't get a chance to clear up its garbage until the
> whole chain is finished.

I am actually running into heap problems for large documents.

I wasn't aware of this limitation, and tend to develop in small steps
that could be merged together: would that help?

Does each step keep a full copy of the result document in memory until
the chain terminates (or only the parts it has modified)?

Thanks,
Regards,
EB

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/saxon-help