qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v3] meson: Pass -j option to sphinx
Date: Sat, 29 Apr 2023 14:33:17 +0200	[thread overview]
Message-ID: <12c1fa01-9c1d-9af7-71eb-e9103346d0af@redhat.com> (raw)
In-Reply-To: <20230428150102.13114-1-farosas@suse.de>

On 4/28/23 17:01, Fabiano Rosas wrote:
> Also make sure our plugins support parallelism and report it properly
> to sphinx. Particularly, implement the merge_domaindata method in
> DBusDomain that is used to merge in data from other subprocesses.
> 
> before:
>    $ time make man html
>    ...
>    [1/2] Generating docs/QEMU manual with a custom command
>    [2/2] Generating docs/QEMU man pages with a custom command
> 
>    real    0m43.157s
>    user    0m42.642s
>    sys     0m0.576s
> 
> after:
>    $ time make man html
>    ...
>    [1/2] Generating docs/QEMU manual with a custom command
>    [2/2] Generating docs/QEMU man pages with a custom command
> 
>    real    0m25.014s
>    user    0m51.288s
>    sys     0m2.085s

The 'nproc' fallback will potentially cause twice #CPUs processes to be 
active, since sphinx will run in parallel with everything else.

Is this result with "-j auto", and if so with which computer?  If the 
speedup is only 2x as it seems to be from the "time" above, I'd rather 
have "-j 2" only so that sphinx doesn't risk killing the machine...

Paolo



  parent reply	other threads:[~2023-04-29 12:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 15:01 [PATCH v3] meson: Pass -j option to sphinx Fabiano Rosas
2023-04-28 15:04 ` Daniel P. Berrangé
2023-04-28 17:14 ` Markus Armbruster
2023-04-28 17:45   ` Fabiano Rosas
2023-05-02  6:32     ` Thomas Huth
2023-04-29 12:33 ` Paolo Bonzini [this message]
2023-05-02  8:34   ` Daniel P. Berrangé
2023-05-02 13:06     ` Fabiano Rosas

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=12c1fa01-9c1d-9af7-71eb-e9103346d0af@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=marcandre.lureau@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).