John Austin wrote:
Why bother implementing reset() ?
Reusing the driver keeps the element mappings and perhaps some
other settings which are expensive to build (building element
settings involves reading service files from the jar and populating
some *big* has tables).
J.Pietschmann
John Austin wrote:
> I still object to the extreme high water marks in FOP. The saw-tooth
> pattern is described in the JMP documentation as characteristic of
> the creation of too many objects. This is probably fundamental to
> XSL-FO but the high-water mark of memory use would be lower if object
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
--- 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
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' rep
On Fri, 2003-11-21 at 15:50, J.Pietschmann wrote:
> John Austin wrote:
> > It is clear that there is a fair bit of memory freed by Driver.reset().
> >
> > After thinking it over, I modified the same test to skip reset() and
> > just null the reference and issue System.gc().
> >
> > This should b
John Austin wrote:
It is clear that there is a fair bit of memory freed by Driver.reset().
After thinking it over, I modified the same test to skip reset() and
just null the reference and issue System.gc().
This should be the same as letting it go out of scope (which happens
afterwards but this w
John Austin wrote:
After reading the Sept 2003 thread about Memory Performance, leaks (and
how wonderful ADA is),
As one of the perpetrators of that thread, I need to mention that I
never finished telling the story. The last analysis I ran seemed to
indicate that it was my image loading code, no
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;
}
Apparentl
On Fri, 2003-11-21 at 00:02, Glen Mazza wrote:
> Please do not cross-post to both lists--keep
> development-related issues on fop-dev.
Sorry. Not something I do a lot.
It was posted to fop-user to be available in the
archives for anyone searching on memory useage.
Users will want to make sure th
Please do not cross-post to both lists--keep
development-related issues on fop-dev.
Thanks,
Glen
--- John Austin <[EMAIL PROTECTED]> wrote:
> After reading the Sept 2003 thread about Memory
__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo
After reading the Sept 2003 thread about Memory Performance, leaks (and
how wonderful ADA is), I modified my test program that generates
3 PDF files. The program now sleeps 30 seconds, calls Driver.reset(),
nulls the reference and sleeps again. In JMP this plots a square wave
between that you can r
12 matches
Mail list logo
