From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Bitbake PSI checker
Date: Mon, 12 Dec 2022 11:07:56 +0100 [thread overview]
Message-ID: <jwq5yegq5h5.fsf@axis.com> (raw)
Hi,
I've been looking into using the pressure stall information awareness of
bitbake but I have some problems getting it to work. Actually I think
it just doesn't work at all.
Reading the code I find that
runqueue.QunQueueScheduler.exceeds_max_pressure claims to "Monitor the
difference in pressure at least once per second". But using some
debugprints added to that method I see output like
1670840023.757171 cpu_pressure 0.0 io_pressure 0.0 mem_pressure 0.0
1670840023.758697 cpu_pressure 0.0 io_pressure 0.0 mem_pressure 0.0
1670840023.760158 cpu_pressure 0.0 io_pressure 0.0 mem_pressure 0.0
1670840023.761733 cpu_pressure 0.0 io_pressure 0.0 mem_pressure 0.0
1670840023.959357 cpu_pressure 969.0 io_pressure 16135.0 mem_pressure 0.0
1670840042.384582 cpu_pressure 8978077.0 io_pressure 1353882.0 mem_pressure 20922.0
1670840042.384582 cpu io pressure exceeded over 18.677629 seconds
1670840042.486946 cpu_pressure 466.0 io_pressure 30792.0 mem_pressure 0.0
1670840042.490340 cpu_pressure 466.0 io_pressure 30792.0 mem_pressure 0.0
where the first column is the value of 'now', and the pressure values
are the calculated deltas. The 0-pressure values are probably because
this is very early in the run and the time delta is less than 0.01
seconds.
But there is a time delta of almost 19 seconds between line 5 and 6, and
unsurprisingly the pressure exceeds my max settings of CPU:600000 and
IO:200000.
But the very next check is only 0.1 second later and while the
prev-values wont be updated, the calculated pressure will be used. This
pressure will be below my settings and a new task will be started.
Am I missing something here? If the pressure should be monitored each
second, isn't it reasonable to have some sort of tick to update the
pre-values? And using the pressure delta of intervals of less than a
second also seems to give too low pressure values.
/Ola Nilsson
next reply other threads:[~2022-12-12 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:07 Ola x Nilsson [this message]
2022-12-12 20:48 ` [bitbake-devel] Bitbake PSI checker Randy MacLeod
2022-12-19 12:50 ` Ola x Nilsson
2022-12-19 19:49 ` contrib
2023-05-20 19:58 ` Randy MacLeod
2023-05-22 2:17 ` ChenQi
2023-05-22 9:36 ` Ola x Nilsson
2023-05-22 14:41 ` Randy MacLeod
2023-05-23 2:08 ` Chen, Qi
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=jwq5yegq5h5.fsf@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=bitbake-devel@lists.openembedded.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 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).