From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"t.lamprecht@proxmox.com" <t.lamprecht@proxmox.com>,
"aderumier@odiso.com" <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH-SERIES cluster/common/qemu-server/lxc/manager] add new metric stats in single rrd
Date: Sat, 28 May 2022 17:11:55 +0000 [thread overview]
Message-ID: <d7b841e1142a72505643072e66143d9f6c64d353.camel@groupe-cyllene.com> (raw)
In-Reply-To: <5f106d7e-5d74-f9be-f30f-cbbf15aedd85@proxmox.com>
Hi Thomas,
for pressure, I don't really need rrd or history, as I can already
broadcast last 10s,60s, 300s.
so could simply broadcast them in kvstore.
This was the original patch in 2020
https://lists.proxmox.com/pipermail/pve-devel/2020-October/045493.html
but Dietmar asked about to put them in rrd ;)
So, as you want, just tell me :)
I don't care about rrd for my need.
Anyway, For vm balancing, I was planning to compute average metric
instead parsing at lot of rrd.
for ksm, I really need current value
for qemu hostcpu/hostmem, last (1-5) minutes average could be enough,
so I could compute from pvestatd too.
Alexandre
Le mercredi 25 mai 2022 à 17:03 +0200, Thomas Lamprecht a écrit :
> On 25/05/2022 08:52, Alexandre Derumier wrote:
> > Hi,
> >
> > I'm still working on vm balancing/scheduling, and need some new
> > metrics.
> >
>
> but you don't actually need the metrics themselves but only the
> computed
> moving avg result and such of them? Because if that's the case we
> could just
> keep the last X values we require for the moving window cached
> locally in
> pvestatd and use those to broadcast the calculated ones use for DRS
> once or
> twice every minute or so via the per-node kv status in the pvestatd?
>
> Could mean less data an no new RRD format/paths (iow. no touching of
> pve-cluster at all). What do you think?
>
>
prev parent reply other threads:[~2022-05-28 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:52 Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-cluster 1/1] add pve2-metrics rrd (single metrics) Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-common 1/2] cgroup: get_pressure_stat: use controllers in get_path Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-manager 1/3] pvestatd: qemu/lxc/host : broadcast rrd pressure metrics Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH qemu-server 1/3] vmstatus: add hostcpu value Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-container 1/1] vmstatus: add pressure stats Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-common 2/2] cgroup: get_pressure_stat: add cpu full pressure Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-manager 2/3] pvestatd: qemu: broadcast rrd hostcpu && hostmem metrics Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH qemu-server 2/3] vmstatus: add hostmem value Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH pve-manager 3/3] pvestatd: host: broadcast rrd ksm metric Alexandre Derumier
2022-05-25 6:52 ` [pve-devel] [PATCH qemu-server 3/3] vmstatus: add pressure stats Alexandre Derumier
2022-05-25 15:03 ` [pve-devel] [PATCH-SERIES cluster/common/qemu-server/lxc/manager] add new metric stats in single rrd Thomas Lamprecht
2022-05-28 17:11 ` DERUMIER, Alexandre [this message]
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=d7b841e1142a72505643072e66143d9f6c64d353.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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 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.