Building documentation with Docbook-DSSSL-Modular
v1.77 has slowed down dramatically (by a factor
of 20x) compared to version 1.73 of these stylesheets.
More info on the problem, from an email I got about debian
bug 156241:
I have since figured out something that causes the symptom;
it leads to
changing documents' contents, as opposed to fixing DSSSL code.
The "extreme slowness" occurs when I set up <literallayout>
environments in
documents where the material being made "literal" is
directly presented in the
document.
If I replace this with inclusions pulled in from outside
files, there's not
the same slowness:
I'm guessing that when Jade/DSSSL are processing text files,
they can
efficiently look at the data on a line-by-line basis, but
when the material is
in the local document, the processor has to do something
vastly less
efficient, perhaps walking through the entire document to
find the CDATA. But
that's just a guess...
At any rate, I moved all of my "literals" out to files that
get drawn in as
inlinegraphic elements and things sped up spectacularly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=88882
This problem seems to be being triggered when
%indent-program-lines% or %indent-screen-lines% is not #f.
In other words, function $verbatim-line-by-line$ has
slowed down dramatically.
Logged In: YES
user_id=18375
More info on the problem, from an email I got about debian
bug 156241:
I have since figured out something that causes the symptom;
it leads to
changing documents' contents, as opposed to fixing DSSSL code.
The "extreme slowness" occurs when I set up <literallayout>
environments in
documents where the material being made "literal" is
directly presented in the
document.
If I replace this with inclusions pulled in from outside
files, there's not
the same slowness:
<literallayout><literal remap="tt"><inlinegraphic
fileref="inclusion.txt"
format="linespecific"></literal></literallayout>
I'm guessing that when Jade/DSSSL are processing text files,
they can
efficiently look at the data on a line-by-line basis, but
when the material is
in the local document, the processor has to do something
vastly less
efficient, perhaps walking through the entire document to
find the CDATA. But
that's just a guess...
At any rate, I moved all of my "literals" out to files that
get drawn in as
inlinegraphic elements and things sped up spectacularly.
Logged In: YES
user_id=178336
Please provide a test document that shows the problem.