public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: zlang@redhat.com, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 09/12] generic/251: constrain runtime via time/load/soak factors
Date: Tue, 19 Nov 2024 07:50:22 -0800	[thread overview]
Message-ID: <20241119155022.GO9425@frogsfrogsfrogs> (raw)
In-Reply-To: <ZzvtoVID2ASv4IM2@dread.disaster.area>

On Tue, Nov 19, 2024 at 12:45:05PM +1100, Dave Chinner wrote:
> On Mon, Nov 18, 2024 at 03:03:43PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > On my test fleet, this test can run for well in excess of 20 minutes:
> > 
> >    613 generic/251
> >    616 generic/251
> >    624 generic/251
> >    630 generic/251
> >    634 generic/251
> >    652 generic/251
> >    675 generic/251
> >    749 generic/251
> >    777 generic/251
> >    808 generic/251
> >    832 generic/251
> >    946 generic/251
> >   1082 generic/251
> >   1221 generic/251
> >   1241 generic/251
> >   1254 generic/251
> >   1305 generic/251
> >   1366 generic/251
> >   1646 generic/251
> >   1936 generic/251
> >   1952 generic/251
> >   2358 generic/251
> >   4359 generic/251
> >   5325 generic/251
> >  34046 generic/251
> > 
> > because it hardcodes 20 threads and 10 copies.  It's not great to have a
> > test that results in a significant fraction of the total test runtime.
> > Fix the looping and load on this test to use LOAD and TIME_FACTOR to
> > scale up its operations, along with the usual SOAK_DURATION override.
> > That brings the default runtime down to less than a minute.
> > 
> > Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> 
> Question for you: Does your $here directory contain a .git subdir?
> 
> One of the causes of long runtime for me has been that $here might
> only contain 30MB of files, but the .git subdir balloons to several
> hundred MB over time, resulting is really long runtimes because it's
> copying GBs of data from the .git subdir.
> 
> I have this patch in my tree:
> 
> --- a/tests/generic/251
> +++ b/tests/generic/251
> @@ -175,9 +175,12 @@ nproc=20
>  # Copy $here to the scratch fs and make coipes of the replica.  The fstests
>  # output (and hence $seqres.full) could be in $here, so we need to snapshot
>  # $here before computing file checksums.
> +#
> +# $here/* as the files to copy so we avoid any .git directory that might be
> +# much, much larger than the rest of the fstests source tree we are copying.
>  content=$SCRATCH_MNT/orig
>  mkdir -p $content
> -cp -axT $here/ $content/
> +cp -ax $here/* $content/
> 
>  mkdir -p $tmp
> 
> And that's made the runtime drop from (typically) 10-15 minutes
> down to around 5 minutes....
> 
> Does this have any impact on the runtime on your test systems?

Nope, I do vpath builds (sort of) so there's no .git history getting
sucked up by generic/251.  The fstests directory on the test VMs is
~34MB spread across ~4800 files.

--D

> -Dave.
> 
> -- 
> Dave Chinner
> david@fromorbit.com
> 

  parent reply	other threads:[~2024-11-19 15:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 23:01 [PATCHSET] fstests: random fixes for v2024.11.17 Darrick J. Wong
2024-11-18 23:01 ` [PATCH 01/12] generic/757: fix various bugs in this test Darrick J. Wong
2024-11-21  9:56   ` Zorro Lang
2024-11-21 10:05     ` Christoph Hellwig
2024-11-21 10:13       ` Christoph Hellwig
2024-11-21 10:52         ` Christoph Hellwig
2024-11-21 16:33           ` Darrick J. Wong
2024-11-21 17:19             ` Darrick J. Wong
2024-11-22 12:35               ` Christoph Hellwig
2024-11-21 12:28       ` Brian Foster
2024-11-21 13:12         ` Christoph Hellwig
2024-11-21 14:11           ` Brian Foster
2024-11-22 12:31             ` Christoph Hellwig
2024-11-22 13:49               ` Brian Foster
2024-11-22 16:13                 ` Darrick J. Wong
2024-11-22 16:20                   ` Christoph Hellwig
2024-11-22 16:33                   ` Brian Foster
2024-11-22 16:37                     ` Darrick J. Wong
2024-11-21 16:04         ` Darrick J. Wong
2024-11-22 12:34           ` Christoph Hellwig
2024-11-18 23:01 ` [PATCH 02/12] xfs/113: fix failure to corrupt the entire directory Darrick J. Wong
2024-11-18 23:02 ` [PATCH 03/12] xfs/508: fix test for 64k blocksize Darrick J. Wong
2024-11-18 23:02 ` [PATCH 04/12] common/rc: capture dmesg when oom kills happen Darrick J. Wong
2024-11-18 23:02 ` [PATCH 05/12] generic/562: handle ENOSPC while cloning gracefully Darrick J. Wong
2024-11-19  0:17   ` Filipe Manana
2024-11-19  0:31     ` Darrick J. Wong
2024-11-25  5:18       ` Darrick J. Wong
2024-11-18 23:02 ` [PATCH 06/12] xfs/163: skip test if we can't shrink due to enospc issues Darrick J. Wong
2024-11-19  6:11   ` Christoph Hellwig
2024-11-18 23:03 ` [PATCH 07/12] xfs/009: allow logically contiguous preallocations Darrick J. Wong
2024-11-19  6:11   ` Christoph Hellwig
2024-11-18 23:03 ` [PATCH 08/12] generic/251: use sentinel files to kill the fstrim loop Darrick J. Wong
2024-11-19  6:11   ` Christoph Hellwig
2024-11-18 23:03 ` [PATCH 09/12] generic/251: constrain runtime via time/load/soak factors Darrick J. Wong
2024-11-19  1:45   ` Dave Chinner
2024-11-19  6:13     ` Christoph Hellwig
2024-11-19 15:45       ` Darrick J. Wong
2024-11-19 21:04         ` Dave Chinner
2024-11-19 21:16           ` Darrick J. Wong
2024-11-19 15:50     ` Darrick J. Wong [this message]
2024-11-18 23:03 ` [PATCH 10/12] common/rc: _scratch_mkfs_sized supports extra arguments Darrick J. Wong
2024-11-18 23:04 ` [PATCH 11/12] xfs/157: do not drop necessary mkfs options Darrick J. Wong
2024-11-21 10:03   ` Zorro Lang
2024-11-18 23:04 ` [PATCH 12/12] xfs/157: fix test failures when MKFS_OPTIONS has -L options Darrick J. Wong
2024-11-21 10:17   ` Zorro Lang
2024-11-21 17:19     ` Darrick J. Wong

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=20241119155022.GO9425@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.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