From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ceph osd: ui: show PGs per OSD
Date: Wed, 15 Feb 2023 10:20:21 +0100 [thread overview]
Message-ID: <5eb9fadb-202d-9a1e-6370-e115c0e28915@proxmox.com> (raw)
In-Reply-To: <2563677d-2cf5-16ab-3261-ce270bc8ff0c@proxmox.com>
On 2/15/23 07:18, Thomas Lamprecht wrote:
> Am 14/02/2023 um 17:14 schrieb Aaron Lauterer:
>> Seems like the `osd df tree` call is about 25% slower, plus minus.
>>
>> Tested on our AMD test cluster that is currently set up with 3 nodes with 4 OSDs each. 50k iterations.
>>
>> root@jura1:~# ./bench.pl
>> Rate osd-df-tree osd-tree
>> osd-df-tree 9217/s -- -27%
>> osd-tree 12658/s 37% --
>> root@jura1:~# ./bench.pl
>> Rate osd-df-tree osd-tree
>> osd-df-tree 9141/s -- -25%
>> osd-tree 12136/s 33% --
>> root@jura1:~# ./bench.pl
>> Rate osd-df-tree osd-tree
>> osd-df-tree 9940/s -- -23%
>> osd-tree 12987/s 31% --
>> root@jura1:~# ./bench.pl
>> Rate osd-df-tree osd-tree
>> osd-df-tree 8666/s -- -20%
>> osd-tree 10846/s 25% --
>> root@jura1:~#
>
> Many thanks for the insight, so significantly more than noise but far from problematic.
Yep, and we don't call it all the time, AFAIU when opening the OSD panel and on
manual "Reload"s.
I took another look at the Ceph API but couldn't find a call that might give us
that information as well to check if it would be cheaper to call.
next prev parent reply other threads:[~2023-02-15 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 8:13 Aaron Lauterer
2023-02-14 13:19 ` Thomas Lamprecht
2023-02-14 15:05 ` Aaron Lauterer
2023-02-14 16:14 ` Aaron Lauterer
2023-02-15 6:18 ` Thomas Lamprecht
2023-02-15 9:20 ` Aaron Lauterer [this message]
2023-02-15 11:25 ` [pve-devel] applied: " Thomas Lamprecht
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=5eb9fadb-202d-9a1e-6370-e115c0e28915@proxmox.com \
--to=a.lauterer@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox