public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org, Tim Cuthbertson <ratcheer@gmail.com>,
	Qu Wenruo <wqu@suse.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: Scrub of my nvme SSD has slowed by about 2/3
Date: Tue, 11 Jul 2023 13:47:58 +0200	[thread overview]
Message-ID: <2316165.ElGaqSPkdT@lichtvoll.de> (raw)
In-Reply-To: <9e05c3b9-301c-84c5-385d-6ca4bfa179f4@gmx.com>

Qu Wenruo - 11.07.23, 13:33:50 CEST:
> >> BTW, what's the CPU usage of v6.3 kernel? Is it higher or lower?
> >> And what about the latency?
> > 
> > CPU usage is between 600-700% on 6.3.9, Latency between 50-70 µs.
> > And
> > scrubbing speed is above 2 GiB/s, peaking at 2,27 GiB/s. Later it
> > went down a bit to 1,7 GiB/s, maybe due to background activity.
> 
> That 600~700% means btrfs is taking all its available thread_pool
> (min(nr_cpu + 2, 8)).
> 
> So although the patch doesn't work as expected, we're still limited by
> the csum verification part.
> 
> At least I have some clue now.

Well it would have an additional 800-900% of CPU time left over to use 
on this machine, those modern processors are crazy. But for that it 
would have to use more threads. However if you can make this more 
efficient CPU time wise… all the better.

> > I'd say the CPU usage to result (=scrubbing speed) ratio is much,
> > much better with 6.3. However the latencies during scrubbing are
> > pretty much the same. I even seen up to 0.2 ms.
[…]
> >> If you're interested in more testing, you can apply the following
> >> small diff, which changed the batch number of scrub.
[…]
> > No time for further testing at the moment. Maybe at a later time.
> > 
> > It might be good you put together a test setup yourself. Any
[…]
> Sure, I'll prepare a dedicated machine for this.
> 
> Thanks for all your effort!

You are welcome.

Thanks,
-- 
Martin



  reply	other threads:[~2023-07-11 11:48 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
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 [this message]
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=2316165.ElGaqSPkdT@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=ratcheer@gmail.com \
    --cc=wqu@suse.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