From: Vegard Nossum <vegard.nossum@oracle.com>
To: Donald Hunter <donald.hunter@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: drop the version constraints for sphinx and dependencies
Date: Mon, 18 Mar 2024 17:54:36 +0100 [thread overview]
Message-ID: <41f28393-0211-4448-8add-ad3c55d02210@oracle.com> (raw)
In-Reply-To: <m21q8732wo.fsf@gmail.com>
On 18/03/2024 17:44, Donald Hunter wrote:
> With Sphinx 2.4.4 I always get timings in this ballpark:
>
> % time make htmldocs
> ...
> real 4m5.417s
> user 17m0.379s
> sys 1m11.889s
>
> With Sphinx 7.2.6 it's typically over 9 minutes:
>
> % time make htmldocs
> ...
> real 9m0.533s
> user 15m38.397s
> sys 1m0.907s
Was this running 'make cleandocs' (or otherwise removing the output
directory) in between? Sphinx is known to be slower if you already have
an output directory with existing-but-obsolete data, I believe this is
the case even when switching from one Sphinx version to another. Akira
also wrote about the 7.x performance:
https://lore.kernel.org/linux-doc/6e4b66fe-dbb3-4149-ac7e-8ae333d6fc9d@gmail.com/
> I have an experimental fix that uses a dict for lookups. With the fix, I
> consistently get times in the sub 5 minute range:
Fantastic!
There is a github issue for the C++ domain but I believe it's the same
issue for both C and C++ domains:
https://github.com/sphinx-doc/sphinx/issues/10966
Vegard
next prev parent reply other threads:[~2024-03-18 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:18 [PATCH v2] docs: drop the version constraints for sphinx and dependencies Lukas Bulwahn
2024-03-03 15:17 ` Jonathan Corbet
2024-03-18 16:44 ` Donald Hunter
2024-03-18 16:54 ` Vegard Nossum [this message]
2024-03-18 17:10 ` Donald Hunter
2024-03-19 17:59 ` Donald Hunter
2024-03-21 16:56 ` Donald Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41f28393-0211-4448-8add-ad3c55d02210@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=donald.hunter@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).