After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 119340 - Poor performance of exlt:document for large document
Poor performance of exlt:document for large document
Status: RESOLVED INCOMPLETE
Product: libxslt
Classification: Platform
Component: general
1.0.30
Other Windows
: Normal enhancement
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-07 14:45 UTC by Jeff Beal
Modified: 2006-07-03 19:14 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Jeff Beal 2003-08-07 14:45:49 UTC
As discussed in
http://lists.oasis-open.org/archives/docbook-apps/200308/msg00054.html

If you need a large test-doc, I can send you a flattened copy of our doc.
with all text obfuscated with an xsl:translate() function.
Comment 1 Jeff Beal 2003-08-07 14:57:05 UTC
When doing benchmark comparisons between xsltproc and Saxon I always
used the out-of-the-box DocBook stylesheets without any parameters or
other customizations.  I'm pretty sure the last version of the DocBook
stylesheets I tested with was 1.56.1.
Comment 2 Daniel Veillard 2003-08-10 14:47:12 UTC
Well, first thing I can tell is that using version 1.40 instead of
1.56.1 the processing of a medium document goes from 5 seconds to
3 seconds. Recent versions seems to have introduced far more 
expensive processing.

Daniel
Comment 3 William M. Brack 2004-07-26 18:11:57 UTC
A different bug (http://bugzilla.gnome.org/show_bug.cgi?id=119340) was 
submitted concerning slow output on Windows, and that problem has now been 
fixed in the current CVS.  Could you please check whether that change fixes 
this problem as well?  Thanks.
Comment 4 André Klapper 2006-07-03 19:14:23 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information William asked for.
Thanks!