From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Martin Steigerwald <martin@lichtvoll.de>,
linux-btrfs@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Tim Cuthbertson <ratcheer@gmail.com>
Subject: Re: Scrub of my nvme SSD has slowed by about 2/3
Date: Sat, 9 Sep 2023 06:03:38 +0800 [thread overview]
Message-ID: <4f5fee23-2ccb-41a2-a64c-1675bc378ff5@gmx.com> (raw)
In-Reply-To: <2169630.irdbgypaU6@lichtvoll.de>
On 2023/9/8 19:54, Martin Steigerwald wrote:
> Hi Thorsten, Qu, Tim, everyone,
>
> Linux regression tracking #update (Thorsten Leemhuis) - 29.08.23, 14:17:33
> CEST:
>> On 12.07.23 13:02, Linux regression tracking #adding (Thorsten Leemhuis)
>> wrote:
>>> On 03.07.23 22:19, Tim Cuthbertson wrote:
>>>> 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.
>>>
>>> Thanks for the report. It seems it will take some work to address
>>> this,
>>> so to be sure the issue doesn't fall through the cracks unnoticed, I'm
>>> adding it to regzbot, the Linux kernel regression tracking bot:
>>>
>>> #regzbot ^introduced e02ee89baa66
>>
>> #regzbot resolve: various changes merged for 6.6 improve things again;
>> more planned; backporting is planned, too;
>> #regzbot ignore-activity
>>
>> (yes, that is not idea, but that's how it is sometimes)
>
> ideal?
>
> Scrubbing "/home" with 304.61GiB (interestingly both back then with 6.4
> and now with 6.5.2):
>
> - 6.4: 966.84MiB/s
> - 6.5.2: 748.02MiB/s
>
> I expected an improvement.
>
> Same Lenovo ThinkPad T14 AMD Gen 1 with AMD Ryzen 7 PRO 4750U, 32 GiB RAM
> and 2TB Samsung 980 Pro NVME SSD as before.
The fixes didn't arrive until v6.6.
Thanks,
Qu
>
> Ciao,
next prev parent reply other threads:[~2023-09-08 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAKzf7=yS9vnf5zNid1CyvN19wyAgPz5o9sJP0vBqN6LReqXVg@mail.gmail.com>
2023-07-12 11:02 ` Scrub of my nvme SSD has slowed by about 2/3 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 [this message]
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=4f5fee23-2ccb-41a2-a64c-1675bc378ff5@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=ratcheer@gmail.com \
--cc=regressions@lists.linux.dev \
/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