its prob has something to do with caching
of with the fact that reflection is used
first time to find calss and instantiate it,
but there after its in the class loader
could add a context listener to tomcat startup
and it does the first xform on container startup
-Original Message-
It needs to load a lot libs, (many IOs )
This happens to all java apps. Not Just FOP.
-Original Message-
From: Robert Paris [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 10:55 AM
To: [EMAIL PROTECTED]
Subject: Why is FOP MUCH slower the first time than all other runs?
I'm
]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Why is FOP MUCH slower the first time than all other runs?
Date: Fri, 6 Feb 2004 12:02:00 -0500
its prob has something to do with caching
of with the fact that reflection is used
first time to find calss and instantiate it,
but there after
No, it's not in FOP. George is on the right track and Robert is not that
far away IMO.
FOP is a relatively big package and with a number of dependecies. Lots
of classes take a lot of time to load. After loading they need to be
initialized and then the JIT (Just in time Compiler) clicks in and
Robert Paris wrote:
I don't think it's the tomcat issue, it takes a long time the first time
even when I call it from a java class (if the class creates a pdf then
creates another one before exiting, the second one is much faster). It's
got to be in the FOP. Is there a way to fix this?
1. It
: Why is FOP MUCH slower the first time than all other runs?
Robert Paris wrote:
I don't think it's the tomcat issue, it takes a long time the first
time
even when I call it from a java class (if the class creates a pdf then
creates another one before exiting, the second one is much faster).
It's
Or you can start tomcat and leave it on...
-Original Message-
From: George Yi [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 4:19 PM
To: [EMAIL PROTECTED]
Subject: RE: Why is FOP MUCH slower the first time than all other runs?
One way to work around, you can write an init
