From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-common 1/1] ProcFSTools: add read_pressure
Date: Sun, 11 Oct 2020 10:23:38 +0200 [thread overview]
Message-ID: <CAMGxVzCCQusf3ZkfxV0=CGGoZRJhfwyhtB40zgyq6T+PSjXdRQ@mail.gmail.com> (raw)
In-Reply-To: <20201006115839.1026402-2-aderumier@odiso.com>
Hi,
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
Le mar. 6 oct. 2020 à 13:58, Alexandre Derumier <aderumier@odiso.com> a
écrit :
> read new /proc/pressure/(cpu,disk,io) introduced in kernel 4.20.
>
> This give more granular informations than loadaverage.
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> src/PVE/ProcFSTools.pm | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/src/PVE/ProcFSTools.pm b/src/PVE/ProcFSTools.pm
> index 7cf1472..7687c13 100644
> --- a/src/PVE/ProcFSTools.pm
> +++ b/src/PVE/ProcFSTools.pm
> @@ -132,6 +132,24 @@ sub read_loadavg {
> return wantarray ? (0, 0, 0) : 0;
> }
>
> +sub read_pressure {
> +
> + my $res = {};
> + foreach my $type (qw(cpu memory io)) {
> + if (my $fh = IO::File->new ("/proc/pressure/$type", "r")) {
> + while (defined (my $line = <$fh>)) {
> + if ($line =~
> /^(some|full)\s+avg10\=(\d+\.\d+)\s+avg60\=(\d+\.\d+)\s+avg300\=(\d+\.\d+)\s+total\=(\d+)/)
> {
> + $res->{$type}->{$1}->{avg10} = $2;
> + $res->{$type}->{$1}->{avg60} = $3;
> + $res->{$type}->{$1}->{avg300} = $4;
> + }
> + }
> + $fh->close;
> + }
> + }
> + return $res;
> +}
> +
> my $last_proc_stat;
>
> sub read_proc_stat {
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2020-10-11 8:23 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 [this message]
2020-10-13 6:05 ` Dietmar Maurer
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='CAMGxVzCCQusf3ZkfxV0=CGGoZRJhfwyhtB40zgyq6T+PSjXdRQ@mail.gmail.com' \
--to=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