P.S: I am willing to apply the code changes to my version
of fop(0.20.4), test it and submit the results on my large
fo files.
-Original Message-
From: Martin Poeschl [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 17, 2002 11:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Performance tuning
Hello dear Venu,
Am Donnerstag, 24. Oktober 2002 20:28 schrieb Venu Reddy:
Hi,
What is the current status of this performance tuning.
Have the code changes been submitted and performance benefits
verified. I really could use some speed improvements with fop,
I have some very large reports
willing to apply the code changes to my version
of fop(0.20.4), test it and submit the results on my large
fo files.
-Original Message-
From: Martin Poeschl [mailto:mpoeschl;marmot.at]
Sent: Thursday, October 17, 2002 11:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Performance tuning.
Henrik
Henrik Olsson wrote:
Hi.
I have runned several performance tests on the FOP and and I have found
out several bottle necks (especially in the PropertyListBuilder).
Most things is about reducing gc and some others about not so well written
code.
The result of this tunings gives me a speed of 3
Hi Henrik
I have started the task to create diffs.
Great.
But it makes it a bit complecated since there are about 10 diffrent things
i have done to the code and some things affects more then 20 source files.
So the question are: Do You want all the changes in one bunch or them
diffrent groups that belongs together?
Henrik
Jeremias Maerki [EMAIL PROTECTED]
2002-10-17 10:56
Please respond to fop-dev
To:[EMAIL PROTECTED]
cc:
Subject:Re: Performance tuning.
Henrik,
that sounds very interesting. Normal procedures for sending changes
Hi Henrik,
whatever the FOP-developers say, I'd like
totry andimplement your improvements in the project I'm working on.
3 times as fast, it's a dream come true!
Here's my address: [EMAIL PROTECTED]
Cheers
Guy
- Original Message -
From:
Henrik Olsson
To: [EMAIL PROTECTED]
Henrik,
that sounds very interesting. Normal procedures for sending changes is
to create a unified CVS diff file. You'll find some instructions
following the URL below:
http://xml.apache.org/source.html
It's best if you post the two diff files (against the maintenance branch
and the main
