From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC cluster 1/4] rrd: add free, buffer/cache and arc size to memory statistics
Date: Tue, 12 Dec 2023 07:49:27 +0000 [thread overview]
Message-ID: <adee5959a556804b2355c44585c69d6e217b0e74.camel@groupe-cyllene.com> (raw)
In-Reply-To: <20231211144721.212071-2-f.gleumes@proxmox.com>
Hi,
if we are going to bump the rrd version,
I think it could be great to add pressure stats too.
I have send patches 2 year ago, it can be really usefull to implement
vm balancing/scheduling/node eviction or even simply to diplay graph
to have more information about load.
https://lists.proxmox.com/pipermail/pve-devel/2022-May/053068.html
This patch was with pressure stats in separate rrd, but if you are
bumping the main rrd version, it could be directly integrated.
I can rework the patch if you want.
-------- Message initial --------
De: Folke Gleumes <f.gleumes@proxmox.com>
Répondre à: Proxmox VE development discussion <pve-
devel@lists.proxmox.com>
À: pve-devel@lists.proxmox.com
Objet: [pve-devel] [RFC cluster 1/4] rrd: add free, buffer/cache and
arc size to memory statistics
Date: 11/12/2023 15:47:18
adding values to the rrd format break compatability with the old file.
Therfore the filename/path had to be changed as well.
Signed-off-by: Folke Gleumes <f.gleumes@proxmox.com>
---
src/pmxcfs/status.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/src/pmxcfs/status.c b/src/pmxcfs/status.c
index dc44464..8834644 100644
--- a/src/pmxcfs/status.c
+++ b/src/pmxcfs/status.c
@@ -1130,7 +1130,10 @@ static const char *rrd_def_node[] = {
"DS:cpu:GAUGE:120:0:U",
"DS:iowait:GAUGE:120:0:U",
"DS:memtotal:GAUGE:120:0:U",
+ "DS:memfree:GAUGE:120:0:U",
"DS:memused:GAUGE:120:0:U",
+ "DS:membuffercache:GAUGE:120:0:U",
+ "DS:arcsize:GAUGE:120:0:U",
"DS:swaptotal:GAUGE:120:0:U",
"DS:swapused:GAUGE:120:0:U",
"DS:roottotal:GAUGE:120:0:U",
@@ -1252,7 +1255,7 @@ update_rrd_data(
int skip = 0;
- if (strncmp(key, "pve2-node/", 10) == 0) {
+ if (strncmp(key, "pve8-node/", 10) == 0) {
const char *node = key + 10;
skip = 2;
@@ -1267,12 +1270,12 @@ update_rrd_data(
if (!g_file_test(filename, G_FILE_TEST_EXISTS)) {
- mkdir(RRDDIR "/pve2-node", 0755);
+ mkdir(RRDDIR "/pve8-node", 0755);
int argcount =
sizeof(rrd_def_node)/sizeof(void*) - 1;
create_rrd_file(filename, argcount,
rrd_def_node);
}
- } else if ((strncmp(key, "pve2-vm/", 8) == 0) ||
+ } else if ((strncmp(key, "pve8-vm/", 8) == 0) ||
(strncmp(key, "pve2.3-vm/", 10) == 0)) {
const char *vmid;
next prev parent reply other threads:[~2023-12-12 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 14:47 [pve-devel] [RFC cluster/common/widget-toolkit/manager 0/4] split node memory graph into usage types Folke Gleumes
2023-12-11 14:47 ` [pve-devel] [RFC cluster 1/4] rrd: add free, buffer/cache and arc size to memory statistics Folke Gleumes
2023-12-12 7:49 ` DERUMIER, Alexandre [this message]
2023-12-11 14:47 ` [pve-devel] [RFC common 2/4] add more detailed statistics to memory report Folke Gleumes
2023-12-11 14:47 ` [pve-devel] [RFC widget-toolkit 3/4] add option to display rrd graph as stacking Folke Gleumes
2023-12-11 14:47 ` [pve-devel] [RFC manager 4/4] split ram usage into usage types Folke Gleumes
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=adee5959a556804b2355c44585c69d6e217b0e74.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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