From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] btrfs: add a test case to verify scrub speed throttle works
Date: Thu, 5 Jan 2023 19:04:22 +0800 [thread overview]
Message-ID: <0b132ac5-89dc-7f1a-9d7d-fff198ed4d90@oracle.com> (raw)
In-Reply-To: <20230105071819.44226-1-wqu@suse.com>
On 1/5/23 15:18, Qu Wenruo wrote:
> We introduced scrub speed throttle in commit eb3b50536642 ("btrfs: scrub:
> per-device bandwidth control"), but it is not that well documented
> (e.g. what's the unit of the sysfs interface), nor tested by any test
> case.
>
> This patch will add a test case for this functionality.
>
> The test case itself is pretty straightforward:
>
> - Fill the fs with 2G file as scrub workload
> - Scrub without any throttle to grab the initial speed
> - Set the throttle to half of the initial speed
> - Scrub again and check the speed against the throttle
>
> The test case has an assumption that we can exclusively use all the
> performance of the underlying disk.
> But for cloud environment it's not ensured 100%, thus the test case is
> not included in auto group to avoid false alerts.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
LGTM.
Reviewed-by: Anand Jain <anand.jain@oralce.com>
-
> ---
> Changelog:
> v2:
> - Instead of a hardcoded speed, run scrub to grab the performance and
> set the throttle to half of the original speed
> This reduced the test runtime from 60s to 30s on a SATA SSD.
>
> - Use "btrfs scrub status" to grab raw scrub speed
> The output of "btrfs scrub start -B" can not be switched to raw mode,
> which makes later parsing harder.
> ---
> tests/btrfs/282 | 92 +++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/282.out | 3 ++
> 2 files changed, 95 insertions(+)
> create mode 100755 tests/btrfs/282
> create mode 100644 tests/btrfs/282.out
>
> diff --git a/tests/btrfs/282 b/tests/btrfs/282
> new file mode 100755
> index 00000000..78b56528
> --- /dev/null
> +++ b/tests/btrfs/282
> @@ -0,0 +1,92 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (C) 2023 SUSE Linux Products GmbH. All Rights Reserved.
> +#
> +# FS QA Test 282
> +#
> +# Make sure scrub speed limitation works as expected.
> +#
> +. ./common/preamble
> +_begin_fstest scrub
> +
> +# Override the default cleanup function.
> +# _cleanup()
> +# {
> +# cd /
> +# rm -r -f $tmp.*
> +# }
> +
> +. ./common/filter
> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
> +_supported_fs btrfs
> +_wants_kernel_commit eb3b50536642 \
> + "btrfs: scrub: per-device bandwidth control"
> +
> +# We want at least 5G for the scratch device.
> +_require_scratch_size $(( 5 * 1024 * 1024))
> +
> +_scratch_mkfs >> $seqres.full 2>&1
> +_scratch_mount
> +
> +uuid=$(findmnt -n -o UUID $SCRATCH_MNT)
> +
> +devinfo_dir="/sys/fs/btrfs/${uuid}/devinfo/1"
> +
> +# Check if we have the sysfs interface first.
> +if [ ! -f "${devinfo_dir}/scrub_speed_max" ]; then
> + _notrun "No sysfs interface for scrub speed throttle"
> +fi
> +
> +# Create a 2G file for later scrub workload.
> +# The 2G size is chosen to fit even DUP on a 5G disk.
> +$XFS_IO_PROG -f -c "pwrite -i /dev/urandom 0 2G" $SCRATCH_MNT/file | _filter_xfs_io
> +
> +# Writeback above data, as scrub only verify the committed data.
> +sync
> +
> +# The first scrub, mostly to grab the speed of the scrub.
> +$BTRFS_UTIL_PROG scrub start -B $SCRATCH_MNT >> $seqres.full
> +
> +# We grab the rate from "scrub status" which supports raw bytes reporting
> +#
> +# The output looks like this:
> +# UUID: 62eaabc5-93e8-445f-b8a7-6f027934aea7
> +# Scrub started: Thu Jan 5 14:59:12 2023
> +# Status: finished
> +# Duration: 0:00:02
> +# Total to scrub: 1076166656
> +# Rate: 538083328/s
> +# Error summary: no errors found
> +#
> +# What we care is that Rate line.
> +init_speed=$($BTRFS_UTIL_PROG scrub status --raw $SCRATCH_MNT | grep "Rate:" |\
> + $AWK_PROG '{print $2}' | cut -f1 -d\/)
> +
> +# This can happen for older progs
> +if [ -z "$init_speed" ]; then
> + _notrun "btrfs-progs doesn't support scrub rate reporting"
> +fi
> +
> +# Cycle mount to drop any possible cache.
> +_scratch_cycle_mount
> +
> +target_speed=$(( $init_speed / 2 ))
> +echo "$target_speed" > "${devinfo_dir}/scrub_speed_max"
> +
> +# The second scrub, to check the throttled speed.
> +$BTRFS_UTIL_PROG scrub start -B $SCRATCH_MNT >> $seqres.full
> +speed=$($BTRFS_UTIL_PROG scrub status --raw $SCRATCH_MNT | grep "Rate:" |\
> + $AWK_PROG '{print $2}' | cut -f1 -d\/)
> +
> +# We gave a +- 10% tolerance for the throttle
> +if [ "$speed" -gt "$(( $target_speed * 11 / 10 ))" -o \
> + "$speed" -lt "$(( $target_speed * 9 / 10))" ]; then
> + echo "scrub speed $speed Bytes/s is not properly throttled, target is $target_speed Bytes/s"
> +fi
> +
> +# success, all done
> +status=0
> +exit
> diff --git a/tests/btrfs/282.out b/tests/btrfs/282.out
> new file mode 100644
> index 00000000..8d53e7eb
> --- /dev/null
> +++ b/tests/btrfs/282.out
> @@ -0,0 +1,3 @@
> +QA output created by 282
> +wrote 2147483648/2147483648 bytes at offset 0
> +XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
next prev parent reply other threads:[~2023-01-05 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 7:18 [PATCH] btrfs: add a test case to verify scrub speed throttle works Qu Wenruo
2023-01-05 11:04 ` Anand Jain [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 8:21 Qu Wenruo
2023-01-04 22:17 ` Anand Jain
2023-01-04 23:17 ` Qu Wenruo
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=0b132ac5-89dc-7f1a-9d7d-fff198ed4d90@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--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