From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] bitbake.conf: set BB_NICE_LEVEL to lower task prios
Date: Thu, 22 Aug 2019 14:12:10 +0200 [thread overview]
Message-ID: <798d0abc-3598-2517-340f-628ea81c85a6@siemens.com> (raw)
In-Reply-To: <20190822140303.5cb82737@md1za8fc.ad001.siemens.net>
On 22.08.19 14:03, [ext] Henning Schild wrote:
> Am Thu, 22 Aug 2019 13:24:11 +0200
> schrieb Baurzhan Ismagulov <ibr@radix50.net>:
>
>> On Thu, Aug 22, 2019 at 01:15:21PM +0200, Henning Schild wrote:
>>>>> +BB_NICE_LEVEL ?= "10"
>>>>
>>>> Not set by OE by default. Isn't that something for local tuning?
>>>
>>> I know. But we either carry it in all kas files or centrally in the
>>> bitbake.conf. This could also be a default for kas local.conf
>>> creation ... Just wanted to propose it and hear the feedback.
>>
>> I also think kas could be a better candidate. Performance is the
>> last, but important goal of Isar, why reduce it by default for new
>> users if more experienced users can easily do it locally.
>
> If you are not doing anything else on your machine the niceness will
> not decrease the performance.
BTW, I never experience major issues with running full load like this in
parallel to editors or browsers. Of course, if you have a time sensitive
application running, multimedia etc., you feel the difference. Then I'm usually
just doing "docker update <build_container> --cpus <maxcpus-X>". And I suspect
"--cpu-shares <share>" will do similar things as this nice level, just never tried.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-08-22 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 9:15 Henning Schild
2019-08-22 11:03 ` Jan Kiszka
2019-08-22 11:15 ` Henning Schild
2019-08-22 11:24 ` Baurzhan Ismagulov
2019-08-22 12:03 ` Henning Schild
2019-08-22 12:12 ` Jan Kiszka [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=798d0abc-3598-2517-340f-628ea81c85a6@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.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