Am 16.07.2013 17:34, schrieb Olaf:
> Hi,
> 
> We have documentation for hardware modules that is written in rst and
> translated to HTML with sphinx. 
> 
[snip]
> The building process takes about 10 minutes if i don't change anything
> after the last build (i.e. everything that can be cached should be cached):
> olaf@pc:~/ee/doc$ time make html
> [...]
> real10m27.748s
> user9m30.036s
> sys0m6.932s
> 
> We will be adding lots of new hardware modules soon, which will double
> the amount of documentation...
> 
> Adding stuff to the documentation has become really painful since it
> takes so long before one can review it. So the question is: How can we
> speed this up?

One way to speed it up a bit is skipping the build of the search index.
For my setup, this cut build times by roughly 30% (needs a patch
though), and as we didn't use the built in html search it was very useful.

Removing most of the contents from the prefix/postfix block also helped
a lot. It really hurts to have lots of small .rst files and one huge
file with substitutions defined, as doctools/sphinx reparses them over
and over again, no 'precompiled headers' style parsing. So if you have a
large (and even 500 lines can be large...), include inside your prefix,
try to shrink it, or remove it for a test.

Michael

-- 
Michael Schlenker
Software Architect

CONTACT Software GmbH           Tel.:   +49 (421) 20153-80
Wiener Straße 1-3               Fax:    +49 (421) 20153-41
28359 Bremen
http://www.contact.de/          E-Mail: [email protected]

Sitz der Gesellschaft: Bremen
Geschäftsführer: Karl Heinz Zachries, Ralf Holtgrefe
Eingetragen im Handelsregister des Amtsgerichts Bremen unter HRB 13215

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sphinx-users.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to