All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naohiro Aota <Naohiro.Aota@wdc.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/2] btrfs: zoned: fix bandwidth degradaton
Date: Mon, 18 Dec 2023 16:01:55 +0000	[thread overview]
Message-ID: <cover.1702913643.git.naohiro.aota@wdc.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

Writing sequentially to a huge file on btrfs on a SMR HDD revealed a
decline of the performance (220 MiB/s to 30 MiB/s after 500 minutes). As
shown in the attached plot, current btrfs exponentially drops its
performance.

The drop is because find_free_extent() need to traverse a lot of full block
groups, trying to find a space.

This series fixes the performance drop by choosing a proper block group
from the zone_active_bgs. Since the list does not contain full block
groups, there is no need of traversing the full BGs. 

Naohiro Aota (2):
  btrfs: zoned: split out prepare_allocation_zoned()
  btrfs: zoned: optimize hint byte for zoned allocator

 fs/btrfs/extent-tree.c | 50 +++++++++++++++++++++++++++++++-----------
 1 file changed, 37 insertions(+), 13 deletions(-)

-- 
2.43.0


[-- Attachment #2: btrfs-perf.png --]
[-- Type: image/png, Size: 38633 bytes --]

             reply	other threads:[~2023-12-18 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 16:01 Naohiro Aota [this message]
2023-12-18 16:02 ` [PATCH 1/2] btrfs: zoned: split out prepare_allocation_zoned() Naohiro Aota
2023-12-18 16:02 ` [PATCH 2/2] btrfs: zoned: optimize hint byte for zoned allocator Naohiro Aota
2023-12-18 16:21 ` [PATCH 0/2] btrfs: zoned: fix bandwidth degradaton Johannes Thumshirn
2024-01-04 15:45 ` David Sterba

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=cover.1702913643.git.naohiro.aota@wdc.com \
    --to=naohiro.aota@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.