From: <Mikko.Rapeli@bmw.de>
To: <martin.jansa@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] runqueue: Introduce load balanced task spawning
Date: Tue, 14 Aug 2018 06:32:04 +0000 [thread overview]
Message-ID: <20180814063203.GJ8291@hiutale> (raw)
In-Reply-To: <20180814011119.GA1391@jama>
Just my 2 € cents to the discussion:
we had to limit number of threads because heavy C++ projects were using
all of RAM and causing heavy swapping. Single g++ processes were eating
up to 20 gigabytes of physical ram. It's not just the CPU which is the
limiting factor to parallel task execution.
-Mikko
next prev parent reply other threads:[~2018-08-14 6:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 21:04 [PATCH 0/2] Spawn extra tasks at low CPU worload Andreas Müller
2018-08-13 21:04 ` [PATCH 1/2] runqueue: Move decision if a task can be started to one common place Andreas Müller
2018-08-15 8:37 ` Richard Purdie
2018-08-15 8:43 ` Andreas Müller
2018-08-13 21:04 ` [PATCH 2/2] runqueue: Introduce load balanced task spawning Andreas Müller
2018-08-13 21:20 ` Alexander Kanavin
2018-08-13 21:30 ` Andreas Müller
2018-08-13 22:37 ` Andre McCurdy
2018-08-14 0:11 ` Andreas Müller
2018-08-14 1:01 ` Andre McCurdy
2018-08-14 9:05 ` Andreas Müller
2018-08-14 9:18 ` Alexander Kanavin
2018-08-14 1:11 ` Martin Jansa
2018-08-14 6:32 ` Mikko.Rapeli [this message]
2018-08-14 7:57 ` Andreas Müller
2018-08-14 8:07 ` Alexander Kanavin
2018-08-14 9:43 ` Richard Purdie
2018-08-14 9:45 ` Richard Purdie
2018-08-14 10:28 ` Peter Kjellerstedt
2018-08-14 10:43 ` Andreas Müller
2018-08-14 11:07 ` Alexander Kanavin
2018-08-14 11:03 ` Alexander Kanavin
2018-08-15 12:43 ` Alexander Kanavin
2018-08-15 15:01 ` Andreas Müller
2018-08-15 16:26 ` Alexander Kanavin
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=20180814063203.GJ8291@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin.jansa@gmail.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 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.