public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] docs: Fix the docs build with Sphinx 6.0
Date: Thu, 12 Jan 2023 08:13:25 +0900	[thread overview]
Message-ID: <bdd04f2e-64a4-e3ef-eb4c-3681c6f52c2f@gmail.com> (raw)
In-Reply-To: <e2d98136-3c4c-8910-d116-93070c48474d@gmail.com>

On Tue, 10 Jan 2023 00:17:11 +0900, Akira Yokosawa wrote:
> On Mon, 9 Jan 2023 15:14:46 +0100, Martin Liška wrote:
>> Hi.
>>
>> I can confirm the regression, I bisected Sphinx revision that caused that
>> and filled an upstream issues:
>> https://github.com/sphinx-doc/sphinx/issues/11116
> 
> Thank you Martin for looking into this!

Thanks to Martin's inputs on the github issue, Sphinx 6.1.3 has released
and the issue is resolved for parallel builds.

However, for non-parallel builds, the memory hog still remains.
Again, this is a table comparing 5.3.0, 6.1.2, and 6.1.3.

 ======  ===================================  ===============================
                     elapsed time                       maxresident
         -----------------------------------  -------------------------------
 Sphinx     -j1     -j2      -j4      -j6       -j1     -j2     -j4     -j6
 ======  ======== ======== ======== ========  ======= ======= ======= =======
  6.1.3  15:03.83 11:31.99  9:35.15  8:49.01  2949056 1059516  978232  967400
  6.1.2  15:11.74 18:06.89 16:39.93      OOM  2961524 5548344 5255372      --
  5.3.0  14:13.04 10:16.81  8:22.37  8:09.74   711532  937660  846016  800340
 ======  ===================================  ===============================

    Note:
      - The -j1 run needs an explicit option given to sphinx-build:
        make SPHINXOPTS="-q -j1" htmldocs

I naively assumed that the memory hog would be resolved all together,
but that's not the case.

Martin, could you report the remaining issue to upstream Sphinx?

        Thanks, Akira



  reply	other threads:[~2023-01-11 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 20:45 [PATCH] docs: Fix the docs build with Sphinx 6.0 Jonathan Corbet
2023-01-07  5:17 ` Akira Yokosawa
2023-01-08 14:01   ` Mauro Carvalho Chehab
2023-01-09 14:14     ` Martin Liška
2023-01-09 15:17       ` Akira Yokosawa
2023-01-11 23:13         ` Akira Yokosawa [this message]
2023-01-12 16:22           ` Martin Liška
2023-01-14  1:06             ` Akira Yokosawa

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=bdd04f2e-64a4-e3ef-eb4c-3681c6f52c2f@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mliska@suse.cz \
    /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