From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"Venkateswararao Jujjuri" <jvrao@linux.vnet.ibm.com>,
"Andreas Färber" <andreas.faerber@web.de>,
"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v6 5/5] coroutine: add test-coroutine --benchmark-lifecycle
Date: Mon, 27 Jun 2011 10:21:26 +0100 [thread overview]
Message-ID: <1309166486-10530-6-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
In-Reply-To: <1309166486-10530-1-git-send-email-stefanha@linux.vnet.ibm.com>
Add a microbenchmark for coroutine create, enter, and return (aka
lifecycle). This is a useful benchmark because users are expected to
create many coroutines, one per I/O request for example, and we
therefore need to provide good performance in that scenario.
To run:
make test-coroutine
./test-coroutine --benchmark-lifecycle 20000000
This will do 20,000,000 coroutine create, enter, return iterations and
print the resulting time.
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
---
test-coroutine.c | 30 ++++++++++++++++++++++++++++++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/test-coroutine.c b/test-coroutine.c
index 9e9d3c9..bf9f3e9 100644
--- a/test-coroutine.c
+++ b/test-coroutine.c
@@ -150,6 +150,33 @@ static void test_lifecycle(void)
g_assert(done); /* expect done to be true (second time) */
}
+/*
+ * Lifecycle benchmark
+ */
+
+static void coroutine_fn empty_coroutine(void *opaque)
+{
+ /* Do nothing */
+}
+
+static void perf_lifecycle(void)
+{
+ Coroutine *coroutine;
+ unsigned int i, max;
+ double duration;
+
+ max = 1000000;
+
+ g_test_timer_start();
+ for (i = 0; i < max; i++) {
+ coroutine = qemu_coroutine_create(empty_coroutine);
+ qemu_coroutine_enter(coroutine, NULL);
+ }
+ duration = g_test_timer_elapsed();
+
+ g_test_message("Lifecycle %u iterations: %f s\n", max, duration);
+}
+
int main(int argc, char **argv)
{
g_test_init(&argc, &argv, NULL);
@@ -158,5 +185,8 @@ int main(int argc, char **argv)
g_test_add_func("/basic/nesting", test_nesting);
g_test_add_func("/basic/self", test_self);
g_test_add_func("/basic/in_coroutine", test_in_coroutine);
+ if (g_test_perf()) {
+ g_test_add_func("/perf/lifecycle", perf_lifecycle);
+ }
return g_test_run();
}
--
1.7.5.4
next prev parent reply other threads:[~2011-06-27 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 9:21 [Qemu-devel] [PATCH v6 0/5] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-06-27 9:21 ` [Qemu-devel] [PATCH v6 1/5] Add hard build dependency on glib Stefan Hajnoczi
2011-06-27 9:21 ` [Qemu-devel] [PATCH v6 2/5] coroutine: introduce coroutines Stefan Hajnoczi
2011-06-27 9:21 ` [Qemu-devel] [PATCH v6 3/5] coroutine: implement coroutines using gthread Stefan Hajnoczi
2011-06-27 9:21 ` [Qemu-devel] [PATCH v6 4/5] coroutine: add test-coroutine automated tests Stefan Hajnoczi
2011-06-27 9:21 ` Stefan Hajnoczi [this message]
2011-07-16 10:08 ` [Qemu-devel] [PATCH v6 0/5] Coroutines for better asynchronous programming Blue Swirl
2011-07-18 13:09 ` Stefan Hajnoczi
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=1309166486-10530-6-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=andreas.faerber@web.de \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).