From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH pve-common 1/1] ProcFSTools: add read_pressure
Date: Tue, 13 Oct 2020 08:05:00 +0200 (CEST) [thread overview]
Message-ID: <190420382.634.1602569100580@webmail.proxmox.com> (raw)
In-Reply-To: <CAMGxVzCCQusf3ZkfxV0=CGGoZRJhfwyhtB40zgyq6T+PSjXdRQ@mail.gmail.com>
> I have notice that it's possible to get pressure info for each vm/ct
> through cgroups
>
> /sys/fs/cgroup/unified/qemu.slice/<vmid>.scope/cpu.pressure
> /sys/fs/cgroup/unified/lxc/<vmid>/cpu.pressure
>
>
> Maybe it could be great to have some new rrd graphs for each vm/ct ?
> They are very useful counters to known a specific vm/ct is overloaded
I have no idea how reliable this is, because we do not use cgroups v2. But yes,
I think this would be useful.
next prev parent reply other threads:[~2020-10-13 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 11:58 [pve-devel] [PATCH pve-common 0/1] " Alexandre Derumier
2020-10-06 11:58 ` [pve-devel] [PATCH pve-common 1/1] " Alexandre Derumier
2020-10-11 8:23 ` Alexandre Derumier
2020-10-13 6:05 ` Dietmar Maurer [this message]
2020-10-13 6:32 ` Alexandre Derumier
2020-10-13 7:38 ` Dietmar Maurer
2020-10-13 12:05 ` Alexandre Derumier
2020-10-13 5:35 ` [pve-devel] applied: " Dietmar Maurer
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=190420382.634.1602569100580@webmail.proxmox.com \
--to=dietmar@proxmox.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.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