From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, hreitz@redhat.com, kwolf@redhat.com,
jsnow@redhat.com, vsementsov@virtuozzo.com, den@openvz.org
Subject: [PATCH 0/3] iotests: multiprocessing!!
Date: Fri, 3 Dec 2021 13:22:20 +0100 [thread overview]
Message-ID: <20211203122223.2780098-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Finally, I can not stand it any longer. So, I'm happy to present
multiprocessing support for iotests test runner.
testing on tmpfs:
Before:
time check -qcow2
...
real 12m28.095s
user 9m53.398s
sys 2m55.548s
After:
time check -qcow2 -j 12
...
real 2m12.136s
user 12m40.948s
sys 4m7.449s
Hmm, seems -j 6 should be enough. I have 6 cores, 2 threads per core.
Anyway, that's so fast!
Vladimir Sementsov-Ogievskiy (3):
iotests/testrunner.py: add doc string for run_test()
iotests/testrunner.py: move updating last_elapsed to run_tests
iotests: check: multiprocessing support
tests/qemu-iotests/check | 4 +-
tests/qemu-iotests/testrunner.py | 86 ++++++++++++++++++++++++++++----
2 files changed, 80 insertions(+), 10 deletions(-)
--
2.31.1
next reply other threads:[~2021-12-03 12:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:22 Vladimir Sementsov-Ogievskiy [this message]
2021-12-03 12:22 ` [PATCH 1/3] iotests/testrunner.py: add doc string for run_test() Vladimir Sementsov-Ogievskiy
2021-12-06 17:52 ` John Snow
2021-12-10 14:12 ` Kevin Wolf
2021-12-10 14:40 ` Vladimir Sementsov-Ogievskiy
2021-12-03 12:22 ` [PATCH 2/3] iotests/testrunner.py: move updating last_elapsed to run_tests Vladimir Sementsov-Ogievskiy
2021-12-06 17:59 ` John Snow
2021-12-10 14:25 ` Kevin Wolf
2021-12-10 14:47 ` Vladimir Sementsov-Ogievskiy
2021-12-10 20:05 ` Vladimir Sementsov-Ogievskiy
2021-12-03 12:22 ` [PATCH 3/3] iotests: check: multiprocessing support Vladimir Sementsov-Ogievskiy
2021-12-06 18:35 ` John Snow
2021-12-06 20:20 ` Vladimir Sementsov-Ogievskiy
2021-12-06 21:00 ` John Snow
2021-12-10 14:36 ` Kevin Wolf
2021-12-10 14:46 ` Vladimir Sementsov-Ogievskiy
2021-12-10 16:26 ` Kevin Wolf
2021-12-06 18:37 ` [PATCH 0/3] iotests: multiprocessing!! John Snow
2021-12-06 20:26 ` Vladimir Sementsov-Ogievskiy
2021-12-07 18:20 ` John Snow
2021-12-09 14:33 ` Hanna Reitz
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=20211203122223.2780098-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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.