From: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>
To: Ronny Meeus <ronny.meeus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Short process stall after assigning it to a cgroup
Date: Wed, 23 Jun 2021 19:28:11 +0200 [thread overview]
Message-ID: <YNNvK0koEdkuD/z3@blackbook> (raw)
In-Reply-To: <CAMJ=MEegYBi_G=_nk1jaJh-dtJj59EFs6ehCwP5qSBqEKseQ-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hello Ronny.
On Mon, Jun 14, 2021 at 05:29:35PM +0200, Ronny Meeus <ronny.meeus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> All apps are running in the realtime domain and I'm using kernel 4.9
> and cgroup v1. [...] when it enters a full load condition [...]
> I start to gradually reduce the budget of the cgroup until the system
> is idle enough.
Has your application some RT requirements or is there other reason why
you use group RT allocations? (When your app seems to require all CPU
time, you decide to curb it. And it still fullfills RT requirements?)
> But sometimes, immediately after the process assignment, it stops for
> a short period (something like 1 or 2s) and then starts to consume 40%
> again.
What if you reduce cpu.rt_period_us (and cpu.rt_runtime_us
proportionally)? (Are the pauses shorter?) Is there any useful info in
/proc/$PID/stack during these periods?
> Is that expected behavior?
Someone with RT group schedulling knowledge may tell :-)
HTH,
Michal
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-23 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 15:29 Short process stall after assigning it to a cgroup Ronny Meeus
[not found] ` <CAMJ=MEegYBi_G=_nk1jaJh-dtJj59EFs6ehCwP5qSBqEKseQ-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-18 5:32 ` Ronny Meeus
2021-06-23 17:28 ` Michal Koutný [this message]
2021-06-25 7:32 ` Ronny Meeus
[not found] ` <CAMJ=MEfMSX06-mcKuv54T7_VCCrv8uZsN-e-QiHe8-sx-sXVoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-25 8:52 ` Michal Koutný
2021-06-25 11:34 ` Ronny Meeus
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=YNNvK0koEdkuD/z3@blackbook \
--to=mkoutny-ibi9rg/b67k@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ronny.meeus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.