From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org, Tim Cuthbertson <ratcheer@gmail.com>
Subject: Re: Scrub of my nvme SSD has slowed by about 2/3
Date: Tue, 11 Jul 2023 07:33:36 +0200 [thread overview]
Message-ID: <5690570.DvuYhMxLoT@lichtvoll.de> (raw)
In-Reply-To: <CAAKzf7=yS9vnf5zNid1CyvN19wyAgPz5o9sJP0vBqN6LReqXVg@mail.gmail.com>
Tim Cuthbertson - 03.07.23, 22:19:50 CEST:
> Yesterday, I noticed that a scrub of my main system filesystem has
> slowed from about 2.9 gb/sec to about 949 mb/sec. My scrub used to run
> in about 12 seconds, now it is taking 51 seconds. I had just
> installed Linux kernel 6.4.1 on Arch Linux, upgrading from 6.3.9. At
> first I suspected the new kernel, but now I am not so sure.
>
> I have btrfs-progs v 6.3.2-1. It was last upgraded on June 23.
I can confirm this with similar values.
v6.3 was fine, with scrub speeds from 1.8 to 2.6 GiB/s, v6.4 only has a
bit less 1 GiB/s.
atop shows 100% utilization of NVME SSD which is odd at less than 1 GiB/
s sequential I/O and a lot of kworker threads doing about 200-300% of
system time CPU utilization.
This is with ThinkPad T14 AMD Gen 1 with AMD Ryzen 7 PRO 4750U and 32
GiB RAM on Samsung 980 Pro 2TB NVME SSD connected via PCIe 3. The
hardware can definitely do more throughput even with "just" PCIe 3.
--
Martin
next prev parent reply other threads:[~2023-07-11 5:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 20:19 Scrub of my nvme SSD has slowed by about 2/3 Tim Cuthbertson
2023-07-03 23:49 ` Qu Wenruo
2023-07-05 2:44 ` Qu Wenruo
2023-07-11 5:36 ` Martin Steigerwald
2023-07-11 5:33 ` Martin Steigerwald [this message]
2023-07-11 5:49 ` Martin Steigerwald
2023-07-11 5:52 ` Martin Steigerwald
2023-07-11 8:59 ` Qu Wenruo
2023-07-11 9:25 ` Martin Steigerwald
2023-07-11 9:57 ` Qu Wenruo
2023-07-11 10:56 ` Martin Steigerwald
2023-07-11 11:05 ` Qu Wenruo
2023-07-11 11:26 ` Martin Steigerwald
2023-07-11 11:33 ` Qu Wenruo
2023-07-11 11:47 ` Martin Steigerwald
2023-07-14 0:28 ` Qu Wenruo
2023-07-14 6:01 ` Qu Wenruo
2023-07-14 6:58 ` Martin Steigerwald
2023-07-16 9:57 ` Sebastian Döring
2023-07-16 10:55 ` Qu Wenruo
2023-07-16 16:01 ` Sebastian Döring
2023-07-17 5:23 ` Qu Wenruo
2023-07-12 11:02 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-07-19 6:42 ` Martin Steigerwald
2023-07-19 6:55 ` Martin Steigerwald
2023-08-29 12:17 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-09-08 11:54 ` Martin Steigerwald
2023-09-08 22:03 ` Qu Wenruo
2023-09-09 8:06 ` Martin Steigerwald
2023-10-13 13:07 ` Martin Steigerwald
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=5690570.DvuYhMxLoT@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=ratcheer@gmail.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