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-common 1/1] ProcFSTools: add read_pressure
Date: Tue, 13 Oct 2020 14:05:16 +0200	[thread overview]
Message-ID: <CAMGxVzCaKSm5Jg6p3wwoS6vyA3tv7oJ0ahFOiBzUHo2Tc3g+0w@mail.gmail.com> (raw)
In-Reply-To: <786323871.4.1602574695068@webmail.proxmox.com>

>>Why do you need 10s resulution? Isn't 1min good enough?
Well, if the 1min is an average of 10s metric, it's ok.

I'm currently using 1min average and 5min average, so it's not a problem
with current rrds.

Thanks for the informations !


(I'll resend a patch to add pressure to rrd, and also add vm/ct pressure)


Le mar. 13 oct. 2020 à 09:38, Dietmar Maurer <dietmar@proxmox.com> a écrit :

> > BTW, I'm currently playing with reading the rrd files, and I have notice
> than lower precision is 1minute.
> > as pvestatd send values around each 10s, is this 1minute precision an
> average of 6x10s values send by pvestatd ?
>
> Yes (we also store the MAX)
>
> > I'm currently working on a poc of vm balancing, but I would like to have
> something like 15min of 10s precision (90 samples of 10s).
>
> Why do you need 10s resulution? Isn't 1min good enough?
>
> > So currently I'm getting stats each 10s manually
> with PVE::API2Tools::extract_vm_stats like the ressource api.
> > (This use PVE::Cluster::rrd_dump , but I don't understand the ipcc_.
> code. does it only return current streamed values?
> > then after the rrdcached daemon is writing to rrd file the average
> values each minute ?)
> >
> > I don't known if we could have rrd files with 15min of 10s precision ?
> (don't known the write load impact on disks)
>
> We use the following RRD conf, step is 60 seconds (see
> pve-cluster/src/status.c):
>
> static const char *rrd_def_node[] = {
>         "DS:loadavg:GAUGE:120:0:U",
>         "DS:maxcpu:GAUGE:120:0:U",
>         "DS:cpu:GAUGE:120:0:U",
>         "DS:iowait:GAUGE:120:0:U",
>         "DS:memtotal:GAUGE:120:0:U",
>         "DS:memused:GAUGE:120:0:U",
>         "DS:swaptotal:GAUGE:120:0:U",
>         "DS:swapused:GAUGE:120:0:U",
>         "DS:roottotal:GAUGE:120:0:U",
>         "DS:rootused:GAUGE:120:0:U",
>         "DS:netin:DERIVE:120:0:U",
>         "DS:netout:DERIVE:120:0:U",
>
>         "RRA:AVERAGE:0.5:1:70", // 1 min avg - one hour
>         "RRA:AVERAGE:0.5:30:70", // 30 min avg - one day
>         "RRA:AVERAGE:0.5:180:70", // 3 hour avg - one week
>         "RRA:AVERAGE:0.5:720:70", // 12 hour avg - one month
>         "RRA:AVERAGE:0.5:10080:70", // 7 day avg - ony year
>
>         "RRA:MAX:0.5:1:70", // 1 min max - one hour
>         "RRA:MAX:0.5:30:70", // 30 min max - one day
>         "RRA:MAX:0.5:180:70",  // 3 hour max - one week
>         "RRA:MAX:0.5:720:70", // 12 hour max - one month
>         "RRA:MAX:0.5:10080:70", // 7 day max - ony year
>         NULL,
> };
>
> Also See: man rrdcreate
>
> So no, you do not get 10s precission from RRD.
>
>


  reply	other threads:[~2020-10-13 12: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
2020-10-13  6:32       ` Alexandre Derumier
2020-10-13  7:38         ` Dietmar Maurer
2020-10-13 12:05           ` Alexandre Derumier [this message]
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=CAMGxVzCaKSm5Jg6p3wwoS6vyA3tv7oJ0ahFOiBzUHo2Tc3g+0w@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