From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, n@nfraprado.net
Subject: Re: [PATCH 0/2] docs: A couple of automarkup improvements
Date: Sat, 2 Jul 2022 12:27:05 +0900 [thread overview]
Message-ID: <44dd52ee-bf53-ba66-da82-0a90402812a1@gmail.com> (raw)
In-Reply-To: <20220630163630.714673-1-corbet@lwn.net>
On Thu, 30 Jun 2022 10:36:28 -0600, Jonathan Corbet wrote:
> Building the docs takes far too long. Much of the blame for that lies with
> Sphinx, but some of it is under our own control. These two patches
> eliminate a bunch of useless work in the automarkup extension.
>
> Benchmarking Sphinx runs is hard, as the run time can be rather variable.
> I have consistently found about a 15% speedup from these patches, though,
> with no output changes.
>
> Testing was done with Sphinx 4.4.0 and 5.0.2. My systems all have Python
> 3.10 installed, and there does not appear, alas, to be a straightforward
> way to get Sphinx 3.x to run on that version. Versions of Sphinx prior to
> 3.0 will not be affected by these changes.
They look nice improvements, indeed!
On my rather non-performant machine with Python 3.9.2 + Sphinx 5.0.2,
elapsed time of "make htmldocs" decreased about 12% without any difference
in generated HTML files.
For the series:
Tested-by: Akira Yokosawa <akiyks@gmail.com>
Thanks, Akira
>
> Jonathan Corbet (2):
> docs: automarkup: track failed cross-reference attempts
> docs: automarkup: do not look up symbols twice
>
> Documentation/sphinx/automarkup.py | 56 +++++++++++++++++-------------
> 1 file changed, 32 insertions(+), 24 deletions(-)
>
> --
> 2.36.1
prev parent reply other threads:[~2022-07-02 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:36 Jonathan Corbet
2022-06-30 16:36 ` [PATCH 1/2] docs: automarkup: track failed cross-reference attempts Jonathan Corbet
2022-06-30 16:36 ` [PATCH 2/2] docs: automarkup: do not look up symbols twice Jonathan Corbet
2022-07-02 3:27 ` Akira Yokosawa [this message]
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=44dd52ee-bf53-ba66-da82-0a90402812a1@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n@nfraprado.net \
/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
all inboxes | Powered by JetHome®