From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Jiageng Yu <yujiageng734@gmail.com>
Cc: "Xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Benchmarks of Linux based stubdom
Date: Thu, 17 Nov 2011 17:39:20 +0100 [thread overview]
Message-ID: <20111117163920.GF9627@type.bordeaux.inria.fr> (raw)
In-Reply-To: <CAJ0pt17MtRWNa16NbsXbSm_zuvdYzS5DUZ7wZBeM6b_C+m3MGQ@mail.gmail.com>
Jiageng Yu, le Fri 18 Nov 2011 00:17:15 +0800, a écrit :
> Since the periodic achievement is obtained in Linux based stubdom project, I
> am very interesting in the benchmarks of Linux stubdom. To have a good
> comparison with mini-os based stubdom, I want to do the same benchmarks as you
> did in http://www.xen.org/files/xensummitboston08/SamThibault_XenSummit.pdf.
> Please offer me the tools and methods you had used to measure the mini-os based
> stubdom. Any details would be thankful.
There is not too much fancy in there :)
- Inb (Kcy) is maybe the fancy part: the measurement was made with
assembly bits, basically: rdtsc; inb; rdtsc, i.e. something like:
unsigned long t1, t2;
__asm__ volatile("rdtsc" : "=A" (t1))
inb(0x80);
__asm__ volatile("rdtsc" : "=A" (t2))
- Boot time is from xm create up to "foo login:" prompt.
- Disk performance was measured as seen from the guest, I don't remember
exactly how, probably with a simple program working on /dev/xvdb
with O_DIRECT. The CPU% was read from xm top.
- Net performance was measure as seen from the guest, probably with
netperf. The CPU% was also read from xm top. Note the use of the e1000
virtual device, which iirc performed best at the time.
Samuel
prev parent reply other threads:[~2011-11-17 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 16:17 Benchmarks of Linux based stubdom Jiageng Yu
2011-11-17 16:39 ` Samuel Thibault [this message]
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=20111117163920.GF9627@type.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yujiageng734@gmail.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).