all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Aaron Lauterer <a.lauterer@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 07:18:05 +0100	[thread overview]
Message-ID: <2563677d-2cf5-16ab-3261-ce270bc8ff0c@proxmox.com> (raw)
In-Reply-To: <27365ccf-542c-ff70-2e96-aaf92ea4c66d@proxmox.com>

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.



  reply	other threads:[~2023-02-15  6:18 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 [this message]
2023-02-15  9:20       ` Aaron Lauterer
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=2563677d-2cf5-16ab-3261-ce270bc8ff0c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=a.lauterer@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal