All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 1/5] check-parallel: adjust concurrency according to CPU count
Date: Wed, 15 Jan 2025 16:51:12 +1100	[thread overview]
Message-ID: <20250115060258.3951185-2-david@fromorbit.com> (raw)
In-Reply-To: <20250115060258.3951185-1-david@fromorbit.com>

From: Dave Chinner <dchinner@redhat.com>

COncurrency is currently hard coded at 64 worker threads. THis is
too many for small CPU count machines; the idea is to create a
sustained load of roughly one test per CPU as they are mostly single
threaded/single process tests. The number "64" was chosen because
I've been developing this functionality on a 64p VM.

Rather than hard coding the concurrency, probe the number of CPUs
available and create that many running contexts.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
---
 check-parallel | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/check-parallel b/check-parallel
index c85437252..d34c73f66 100755
--- a/check-parallel
+++ b/check-parallel
@@ -13,7 +13,7 @@ export SRC_DIR="tests"
 basedir=$1
 shift
 check_args="$*"
-runners=64
+runners=$(getconf _NPROCESSORS_CONF)
 runner_list=()
 runtimes=()
 
-- 
2.45.2


  reply	other threads:[~2025-01-15  6:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15  5:51 [PATCH 0/5]: CLI and feature improvements for check-parallel Dave Chinner
2025-01-15  5:51 ` Dave Chinner [this message]
2025-01-15  5:51 ` [PATCH 2/5] check: factor out test list building code Dave Chinner
2025-01-15  5:51 ` [PATCH 3/5] check-parallel: use common group list parsing code Dave Chinner
2025-01-15  5:51 ` [PATCH 4/5] check-parallel: add logwrite device support Dave Chinner
2025-01-15  5:51 ` [PATCH 5/5] check-parallel: allow FSTYP selection from the CLI Dave Chinner
2025-01-15  6:29 ` [PATCH 0/5]: CLI and feature improvements for check-parallel Darrick J. Wong
2025-01-15  6:47   ` Darrick J. Wong
2025-01-15  9:54   ` Dave Chinner

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=20250115060258.3951185-2-david@fromorbit.com \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.