Chris Bowditch wrote:
Splitting the table up is the best way to reduce the ratio memory:input size. Also, there have been some tweaks made to the maintenance code in CVS that help improve the memory usage of tables. To use this latest code, you will need to install a CVS client, download the 0.20.5 code from the maintainance branch and then re-compile. See website for further info:
We found that for a complex 23 page print, the memory usage fell from 100 Mb to 75 Mb (rough measurement) by using the CVS-version. The overall performance is much more influenced by the memory usage of the many pages (when rendering to a PageSet which we do instead of rendering to e.g. a PDF) than by the complexity of the tables.
-- Thorbjoern Ravn Andersen "...plus...Tubular Bells!"
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
