Jean-François El Fouly a écrit :
So I hired the team member who's competent in profiler usage next week
but I must say at the moment I'm still stuck :-(
The sysadmins made a tarball from the staging server and copied
everything to a similar server that has full profiling instrumentation
I've done extensive tests about memory allocation with FOP when
implementing the new image loading framework and in my case the memory
was always released. So, some results from a profiler would be helpful.
Anyway, what I meant with my hint was that the iText step might not be
necessary anymore
On May 8, 2008, at 08:40, Jean-François El Fouly wrote:
Hi
Jeremias Maerki a écrit :
And my next problem is to find a way to force memory recycling
after this long and hefty FOP processing, but until further
investigated this is OT ;-)
You probably didn't get my hint earlier but with the
Andreas Delmelle a écrit :
Which Java VM are you using? Practically every time someone tells us
about memory/GC issues, it appears they are using an implementation
other than Sun (IBM, GNU...)
Up to now, we still have to find out why precisely non-Sun VMs have
difficulties with FOP...
On May 8, 2008, at 11:38, Jean-François El Fouly wrote:
Andreas Delmelle a écrit :
Which Java VM are you using? Practically every time someone tells
us about memory/GC issues, it appears they are using an
implementation other than Sun (IBM, GNU...)
Up to now, we still have to find out why
Andreas Delmelle a écrit :
OK. Just curious: Any chance you could test it on another build or
maybe even Java 6?
Probably, if required or useful. Our sys admins are very cooperative ;-)
In my personal experience, optimizing the stylesheet code usually does
not offer much improvement in
On May 8, 2008, at 12:03, Andreas Delmelle wrote:
Hi Jean-François,
On May 8, 2008, at 12:57, Jean-François El Fouly wrote:
Andreas Delmelle a écrit :
OK. Just curious: Any chance you could test it on another build
or maybe even Java 6?
Probably, if required or useful. Our sys admins are
