From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stefan Sterz <s.sterz@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v3 1/2] api: ceph: add applications of each pool to the lspools endpoint
Date: Fri, 21 Oct 2022 09:04:26 +0200 [thread overview]
Message-ID: <bf763498-aa29-d05a-ea01-5e5a0a7dc73f@proxmox.com> (raw)
In-Reply-To: <8f6f8f15-31bd-f6c5-44e3-09b64e749761@proxmox.com>
Am 21/10/2022 um 08:57 schrieb Stefan Sterz:
>> out of interest: how expensive is this, did you check the overhead?
>>
> do you want a specific metric? in my (admittedly small) test setup
> (three vm cluster with 4 cores and 4Gib RAM) it is barely noticeable.
> the api call takes between 18 and 25ms in both cases for me.
>
I mean, with a handful of pools you probably won't (or really should not)
see any difference >50 ms, that would make it a hard case arguing.
Just wondered if many pools (e.g., [10, 100, 1000]) actually increase this
O(n) or if that falls in the noise of the rados monitor query overhead.
I don't expect that is significant, just wondered if you already checked
and got some info on that.
next prev parent reply other threads:[~2022-10-21 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 7:17 Stefan Sterz
2022-10-20 7:17 ` [pve-devel] [PATCH manager v3 2/2] ui: only allow rbd pools to be added as rbd storage Stefan Sterz
2022-10-20 13:00 ` Thomas Lamprecht
2022-10-21 7:02 ` Stefan Sterz
2022-10-21 7:13 ` Thomas Lamprecht
2022-10-20 12:55 ` [pve-devel] [PATCH manager v3 1/2] api: ceph: add applications of each pool to the lspools endpoint Thomas Lamprecht
2022-10-21 6:57 ` Stefan Sterz
2022-10-21 7:04 ` Thomas Lamprecht [this message]
2022-10-21 7:59 ` Stefan Sterz
2022-10-21 9:54 ` Stefan Sterz
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=bf763498-aa29-d05a-ea01-5e5a0a7dc73f@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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.