From: Daniel Wagner <dwagner@suse.de>
To: linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Chaitanya Kulkarni <kch@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro@fastmail.com>,
Daniel Wagner <dwagner@suse.de>
Subject: [RFC v1 0/1] nvme testsuite runtime optimization
Date: Wed, 19 Apr 2023 10:56:42 +0200 [thread overview]
Message-ID: <20230419085643.25714-1-dwagner@suse.de> (raw)
While testing the fc transport I got a bit tired of wait for the I/O jobs to
finish. Thus here some runtime optimization.
With a small/slow VM I got following values:
with 'optimizations'
loop:
real 4m43.981s
user 0m17.754s
sys 2m6.249s
rdma:
real 2m35.160s
user 0m6.264s
sys 0m56.230s
tcp:
real 2m30.391s
user 0m5.770s
sys 0m46.007s
fc:
real 2m19.738s
user 0m6.012s
sys 0m42.201s
base:
loop:
real 7m35.061s
user 0m23.493s
sys 2m54.866s
rdma:
real 8m29.347s
user 0m13.078s
sys 1m53.158s
tcp:
real 8m11.357s
user 0m13.033s
sys 2m43.156s
fc:
real 5m46.615s
user 0m12.819s
sys 1m46.338s
Daniel Wagner (1):
nvme: Limit runtime for verification and limit test image size
common/xfs | 3 ++-
tests/nvme/004 | 2 +-
tests/nvme/005 | 2 +-
tests/nvme/006 | 2 +-
tests/nvme/007 | 2 +-
tests/nvme/008 | 2 +-
tests/nvme/009 | 2 +-
tests/nvme/010 | 5 +++--
tests/nvme/011 | 5 +++--
tests/nvme/012 | 4 ++--
tests/nvme/013 | 4 ++--
tests/nvme/014 | 10 ++++++++--
tests/nvme/015 | 10 ++++++++--
tests/nvme/017 | 2 +-
tests/nvme/018 | 2 +-
tests/nvme/019 | 2 +-
tests/nvme/020 | 2 +-
tests/nvme/021 | 2 +-
tests/nvme/022 | 2 +-
tests/nvme/023 | 2 +-
tests/nvme/024 | 2 +-
tests/nvme/025 | 2 +-
tests/nvme/026 | 2 +-
tests/nvme/027 | 2 +-
tests/nvme/028 | 2 +-
tests/nvme/029 | 2 +-
tests/nvme/031 | 2 +-
tests/nvme/032 | 4 ++--
tests/nvme/034 | 3 ++-
tests/nvme/035 | 4 ++--
tests/nvme/040 | 4 ++--
tests/nvme/041 | 2 +-
tests/nvme/042 | 2 +-
tests/nvme/043 | 2 +-
tests/nvme/044 | 2 +-
tests/nvme/045 | 2 +-
tests/nvme/047 | 2 +-
tests/nvme/048 | 2 +-
38 files changed, 63 insertions(+), 47 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-19 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 8:56 Daniel Wagner [this message]
2023-04-19 8:56 ` [RFC v1 1/1] nvme: Limit runtime for verification and limit test image size Daniel Wagner
2023-04-19 9:34 ` [RFC v1 0/1] nvme testsuite runtime optimization Chaitanya Kulkarni
2023-04-19 9:50 ` Sagi Grimberg
2023-04-19 11:10 ` Daniel Wagner
2023-04-19 13:15 ` Sagi Grimberg
2023-04-19 21:13 ` Chaitanya Kulkarni
2023-04-19 21:11 ` Chaitanya Kulkarni
2023-04-20 8:24 ` Daniel Wagner
2023-04-20 8:31 ` Daniel Wagner
2023-04-19 21:31 ` Chaitanya Kulkarni
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=20230419085643.25714-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro@fastmail.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;
as well as URLs for NNTP newsgroup(s).