Re: Memory measurement -- importance of Driver.reset() in Cocoon - NOT!

2003-11-24 Thread John Austin
I took a further look at some of the JVM options and ran a few more tests. I found a couple of things that may be useful. 1) I have to use -Xmx400m to produce the 2000 page PDF in a large PDF test, 'time' reported: real ~5m user 2m57.880 ... 2) When I added -Xms400m to the same work 'time'

Re: Memory measurement -- importance of Driver.reset() in Cocoon - NOT!

2003-11-24 Thread Glen Mazza
--- John Austin [EMAIL PROTECTED] wrote: My own feeling is that FOP will remain problematic for large documents and this will be especially so in server environments such as Cocoon. We hear you, and we do emphasize performance as one of our main goals [1]. As always, you may wish to add

Re: Memory measurement -- importance of Driver.reset() in Cocoon - NOT!

2003-11-24 Thread John Austin
On Mon, 2003-11-24 at 16:23, Glen Mazza wrote: --- John Austin [EMAIL PROTECTED] wrote: My own feeling is that FOP will remain problematic for large documents and this will be especially so in server environments such as Cocoon. We hear you, and we do emphasize performance as

Re: Memory measurement -- importance of Driver.reset() in Cocoon - NOT!

2003-11-20 Thread John Austin
On Fri, 2003-11-21 at 00:43, John Austin wrote: I mean, I wonder what Cocoon does ? In FOPSerializer: /** * Recycle serializer by removing references */ public void recycle() { super.recycle(); this.driver = null; this.renderer = null; }