From: Akira Yokosawa <akiyks@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
corbet@lwn.net, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 1/1] scripts/sphinx-build-wrapper: allow building PDF files in parallel
Date: Tue, 19 Aug 2025 18:09:20 +0900 [thread overview]
Message-ID: <19f031e5-0060-4957-8cc8-9cd21e7d6304@gmail.com> (raw)
In-Reply-To: <26e5efca73dbd2f863a51018054a749c9e5f5a19.1755540431.git.mchehab+huawei@kernel.org>
On Mon, 18 Aug 2025 20:10:01 +0200, Mauro Carvalho Chehab wrote:
> Use POSIX jobserver when available or -j<number> to run PDF
> builds in parallel, restoring pdf build performance. Yet,
> running it when debugging troubles is a bad idea, so, when
> calling directly via command line, except if "-j" is splicitly
> requested, it will serialize the build.
>
> With such change, a PDF doc builds now takes around 5 minutes
> on a Ryzen 9 machine with 32 cpu threads:
>
> # Explicitly paralelize both Sphinx and LaTeX pdf builds
> $ make cleandocs; time scripts/sphinx-build-wrapper pdfdocs -j 33
>
> real 5m17.901s
> user 15m1.499s
> sys 2m31.482s
>
> # Use POSIX jobserver to paralelize both sphinx-build and LaTeX
> $ make cleandocs; time make pdfdocs
>
> real 5m22.369s
> user 15m9.076s
> sys 2m31.419s
>
> # Serializes PDF build, while keeping Sphinx parallelized.
> # it is equivalent of passing -jauto via command line
> $ make cleandocs; time scripts/sphinx-build-wrapper pdfdocs
>
> real 11m20.901s
> user 13m2.910s
> sys 1m44.553s
>
Sounds promising to me!
I couldn't test this because I couldn't apply your sphinx-build-wrapper
series on top of docs-next. :-/
Which commit does it based on?
Thanks,
Akira
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
> Closes: https://lore.kernel.org/linux-doc/9b3b0430-066f-486e-89cc-00e6f1f3b096@gmail.com/
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> scripts/sphinx-build-wrapper | 141 ++++++++++++++++++++++++++---------
> 1 file changed, 106 insertions(+), 35 deletions(-)
next prev parent reply other threads:[~2025-08-19 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 18:10 [PATCH 0/1] sphinx-build-wrapper: Fix a performance regression Mauro Carvalho Chehab
2025-08-18 18:10 ` [PATCH 1/1] scripts/sphinx-build-wrapper: allow building PDF files in parallel Mauro Carvalho Chehab
2025-08-19 9:09 ` Akira Yokosawa [this message]
2025-08-19 13:21 ` Jonathan Corbet
2025-08-19 14:27 ` Mauro Carvalho Chehab
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=19f031e5-0060-4957-8cc8-9cd21e7d6304@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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).