As Jörg said, you have to take JVM startup into account. That makes the whole thing relatively unpredictable. Measuring times from batch files is ok to get a general idea but not for investigating details. For that you have to write a Java program and execute the transformations several times to make sure all classes are loaded (a lengthy process) and the JVM had a chance to compile some Java code into machine code for faster execution (HotSpot JIT compiler).
On 23.01.2003 23:34:03 Clay Leeds wrote: > That's an intriguing idea. Assuming that it would help trouble-shoot > problems like this, that might be good for this type of testing. Also, I > noticed a difference in the amount of time, when FOP transformed & > rendered the PDF file from start to finish (01:05 for 0.20.4), versus > when xalan-2.0.1 transformed to XML, and then FOP transformed what was > essentially an FO file to PDF (47030ms+1843ms=48873ms). Any idea where > the additional 15+ seconds went? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
