All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Markus Heiser <markus.heiser@darmarit.de>,
	Kees Cook <keescook@chromium.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Sphinx parallel build errors
Date: Tue, 29 Oct 2019 13:10:16 -0700	[thread overview]
Message-ID: <5c7c968d-800f-7d29-e52e-e163ffe2dc8c@infradead.org> (raw)
In-Reply-To: <f6df7edc-74bf-74b3-1dcd-203d74d0787e@darmarit.de>

On 10/29/19 12:57 PM, Markus Heiser wrote:
> Am 29.10.19 um 20:41 schrieb Randy Dunlap:
>>> In the past I run sphinx builds on a small 4GB VM (2cpu) without any problems.
>>> (nowadays) 16 CPU, 16 GB PC with sphinx-build the max load of my whole PC is
>>> about 5GB (*more CPUs need more mem*).
>>>
>>> @Randy you said the build machine hase 8GB .. and how much CPUs?
>>
>> 4.
>>
> 
>>>> Randy, are you able to just use -j2 or similar with your builds to avoid
>>>> this?
>>
>> No, sometimes even -j1 fails with oom-killer. >
>>> @Randy: my first questions are:
>>>
>>> - cpu / mem?
>>> - are OOM-kills when building target htmldocs, pdfdocs or ..?
>>
>> htmldocs
>>
>>> - which py & sphinx version are used? Reference installation see 'virtualenv'
>>>    in [1]
>>
>> Python 2.7.14
>> sphinx-build 1.7.6
> 
> Seems nothing special in your environment .. its strange to me.
> 
> Installing new sphinx-doc will not help, you are fighting with some
> other problems.  Hoped that I can help, but realize that I don't have
> a clue what it is / sorry.

No problem.  Thanks for looking.

-- 
~Randy


      reply	other threads:[~2019-10-29 20:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 21:37 Sphinx parallel build errors Randy Dunlap
2019-10-09 21:40 ` Jonathan Corbet
2019-10-09 22:18   ` Randy Dunlap
2019-10-10  2:30 ` Kees Cook
2019-10-10  3:00   ` Bhaskar Chowdhury
2019-10-10 18:48   ` Jonathan Corbet
2019-10-10 20:15     ` Randy Dunlap
2019-10-27 18:11       ` Randy Dunlap
2019-10-27 18:17         ` Jonathan Corbet
2019-10-27 18:30           ` Randy Dunlap
2019-10-27 19:05             ` Mauro Carvalho Chehab
2019-10-27 19:36               ` Randy Dunlap
2019-10-28 19:07               ` Kees Cook
2019-10-29  8:16                 ` Markus Heiser
2019-10-29 16:09                   ` Kees Cook
2019-10-29 19:41                   ` Randy Dunlap
2019-10-29 19:57                     ` Markus Heiser
2019-10-29 20:10                       ` Randy Dunlap [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=5c7c968d-800f-7d29-e52e-e163ffe2dc8c@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.