, November 12, 2005 8:43 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Large PDF - Performance
On Nov 12, 2005, at 01:03, Danny wrote:
Hi,
Ok, so continuing from where I was.
I plugged saxon into my application (JAVA) code.
snip /
So that all worked great, for a little while.
Now the report
Danny wrote:
Nothing else changed that I am aware of.
I'm working with it now, I'm sure it is something obvious, I just don't see
it yet.
I am using fop 0.20.5.
I read in some of the mail list messages that there is a fix for some memory
leak? problems in fop trunk involving tables.
The
On Nov 12, 2005, at 01:03, Danny wrote:
Hi,
Ok, so continuing from where I was.
I plugged saxon into my application (JAVA) code.
snip /
So that all worked great, for a little while.
Now the report is taking as long as it did before for some reason
and I have
no idea why.
Strange
@xmlgraphics.apache.org
Subject: Re: Large PDF - Performance
On Nov 10, 2005, at 21:10, J.Pietschmann wrote:
Andreas L Delmelle wrote:
Oh, you might want to look into pre-compiled stylesheets, too. Saxon
supports those. I don't know about Xalan.
It does: see http://xml.apache.org/xalan-j/xsltc_usage.html
Well
I tested several XSLT processors last year - on both Linux and Windows.
I also found that certain XPATH expressions produced significant
differences in processing time between the different processors.
(One surprise was that Saxon 6.5.3 (I think) took a long time with XPATH
expressions
Suite 215
Norcross Ga, 30092
-Original Message-
From: Mike Trotman [mailto:[EMAIL PROTECTED]
Sent: Friday, November 11, 2005 8:54 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Large PDF - Performance
I tested several XSLT processors last year - on both Linux and Windows.
I also
On Nov 11, 2005, at 15:27, Danny wrote:
I plugged saxon into my application code.
1000 TRANSACTION element report (report button click in application
to pdf
display to user)
Before using xalan (4 minutes 20 seconds)
Now using saxon (1 minute 45 seconds)
Quite a difference!
In this
In this respect, it may prove worthwhile to track down whether
this difference is really caused by the XSLT processor itself,
or merely by the fact that Saxon comes bundled with its own
XML parser (AElfred).
From the Aelfred web site on Sourceforge:
Saxon versions from 7.2 onwards no longer
Andreas L Delmelle wrote:
In this respect, it may prove worthwhile to track down whether this
difference is really caused by the XSLT processor itself, or merely by
the fact that Saxon comes bundled with its own XML parser (AElfred).
Saxon uses a more efficient internal data storage, and also
:[EMAIL PROTECTED]
Sent: Friday, November 11, 2005 4:18 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Large PDF - Performance
Andreas L Delmelle wrote:
In this respect, it may prove worthwhile to track down whether this
difference is really caused by the XSLT processor itself, or merely
On Nov 10, 2005, at 18:39, Danny wrote:
Hi,
I cannot seem to get the performance that I need for this report.
I have tried all of the suggestions that I have found, mostly:
removal of the # of n page numbering
multiple page-sequences
Right now it takes 4 min 13 sec (from command line) to
On Nov 10, 2005, at 19:57, [EMAIL PROTECTED] wrote:
snip /
Oh, you might want to look into pre-compiled stylesheets, too. Saxon
supports those. I don't know about Xalan.
It does: see http://xml.apache.org/xalan-j/xsltc_usage.html
Greetz,
Andreas
Andreas L Delmelle wrote:
Oh, you might want to look into pre-compiled stylesheets, too. Saxon
supports those. I don't know about Xalan.
It does: see http://xml.apache.org/xalan-j/xsltc_usage.html
Well, XSLTC compiles XSLT into Java. Compiled style sheets are usually
a bit less drastic, it
On Nov 10, 2005, at 21:10, J.Pietschmann wrote:
Andreas L Delmelle wrote:
Oh, you might want to look into pre-compiled stylesheets, too. Saxon
supports those. I don't know about Xalan.
It does: see http://xml.apache.org/xalan-j/xsltc_usage.html
Well, XSLTC compiles XSLT into Java. Compiled
14 matches
Mail list logo
