Re: [xep-support] performance&limits

Hi,

I had been experiencing some problems while generating large documents (about 5000 pages),
and discovered it actually depends on the way your xsl-fo code is written...

XEP actually stores page-sequences in java memory stack, and it starts writing it (thus freeing the stack) once the whole page-sequence is cached...
so the trick is to write as many page-sequences as possible, containing as few pages as possible.

You can also add custom memory usage params to the xep java command (in xep.sh), adding -Xmx and -Xms arguments
to set respectively the minimum and maximum memory to use for this process.

I've successfully generated 5000 pages PDF with images for the last 2 years, on a standard Dell Laptop with
3Go RAM...

Hope this helps.

= = = ======= = = =

Guillaume Séjourné
Technical Writer

= = = ======= = = =

----- Original Message -----
From: "Curelaru Cristian" <Curelaru_Cristian@emc.com>
To: xep-support@renderx.com
Sent: Wednesday, 25 February, 2009 17:15:51 GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: [xep-support] performance&limits

Hi,

I was wondering if there is some benchmarking information out there.

For example, what time (ball-park) should I expect for a 1000 page PDF (w 300 images)? Let’s assume a decent machine, dual-core processor, enough RAM, 32-bit OS.

I have another question regarding the limits of what RenderX can process on a 32 bit OS. Is there anyway RenderX would handle a 7000 page PDF? What might be the limit?

I do recall seeing somewhere a comment that RenderX requires around 1M per page of memory. I am assuming we are talking about memory that won’t be released until the PDF is out.

Thank you,

Cristian Curelaru

EMC

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Thu Feb 26 01:01:19 2009