public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexandre Derumier <aderumier@odiso.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager] pvestatd: stream host pressure counters
Date: Fri, 23 Oct 2020 01:53:38 +0200	[thread overview]
Message-ID: <CAMGxVzAM2f1sbUZKwkSJ+bhRf6Zt1xbfRZnVwWAk2owJvOwZxg@mail.gmail.com> (raw)
In-Reply-To: <589366911.632.1602568628596@webmail.proxmox.com>

Hi Dietmar,

I would like also to add some improvement for vm memory/cpu stats.

for cpu, currently, we only monitor the qemu process cpu usage, but
with virtio-net + vhost-net,
we are missing vhost-* process cpu usage.  (For vms will a lot of
traffic, this is really signifiant).

I would like to add something like "hostcpu" counter, will real metric
(reading the vm cgroup cpu.stat)

Also, for memory, when ballooning is enabled, we don't have anymore
the real memory usage on the host.
For example, a windows vm with 16g mem is filling memory with zeroes
at boot, so from the host all the 16G memory is used, but in windows
guest we only see something like 2G.

so, I would like to add something like "hostmemory" counter


what do you think about this ?


Le mar. 13 oct. 2020 à 07:57, Dietmar Maurer <dietmar@proxmox.com> a écrit :
>
> I wonder if we want to store that information with RRD instead?
>
> > On 10/06/2020 1:58 PM Alexandre Derumier <aderumier@odiso.com> wrote:
> >
> >
> > Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> > ---
> >  PVE/Service/pvestatd.pm | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
> > index 5e533ca3..238c36ae 100755
> > --- a/PVE/Service/pvestatd.pm
> > +++ b/PVE/Service/pvestatd.pm
> > @@ -161,12 +161,16 @@ sub update_node_status {
> >      );
> >      PVE::Cluster::broadcast_rrd("pve2-node/$nodename", $data);
> >
> > +    my $pressure = PVE::ProcFSTools::read_pressure();
> > +    PVE::Cluster::broadcast_node_kv("pressure", encode_json($pressure));
> > +
>



  reply	other threads:[~2020-10-22 23:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 11:58 Alexandre Derumier
2020-10-13  5:57 ` Dietmar Maurer
2020-10-22 23:53   ` Alexandre Derumier [this message]
2020-10-23  7:50     ` Dietmar Maurer
2020-10-24 13:46       ` Alexandre Derumier
2020-10-24 15:43         ` Thomas Lamprecht
2020-10-26  7:55           ` Alexandre Derumier

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=CAMGxVzAM2f1sbUZKwkSJ+bhRf6Zt1xbfRZnVwWAk2owJvOwZxg@mail.gmail.com \
    --to=aderumier@odiso.com \
    --cc=dietmar@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal