From: Keir Fraser <keir@xensource.com>
To: "Nick L. Petroni Jr." <npetroni@cs.umd.edu>,
xen-devel@lists.xensource.com
Cc: Michael Hicks <mwh@cs.umd.edu>
Subject: Re: Xen Benchmarking guidelines
Date: Tue, 14 Aug 2007 11:53:36 +0100 [thread overview]
Message-ID: <C2E74840.1429C%keir@xensource.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708140545250.6754@localhost>
On 14/8/07 11:37, "Nick L. Petroni Jr." <npetroni@cs.umd.edu> wrote:
> In general, I'm using standard benchmarking best practices, i.e.,
> disabling unnecessary services in host and guest, etc. Perhaps this is
> related to VCPU scheduling? Should I try pinning a vcpu? Please let
> me know if I can provide more details. Any help or insight would be much
> appreciated!
It should be possible, and in fact difficult not, to get almost native
scores on SPECINT benchmarks from within an HVM guest. There's no I/O or
system activity at all -- it's just measuring raw CPU speed.
The most likely culprits are scheduling problems or time problems in the HVM
guest.
To discount scheduling issues, it's probably worth pinning your HVM VCPU to
a single physical CPU (and set the affinity of dom0 so that it *doesn't* run
on that physical CPU) and see if that helps.
For time issues, you can time your SPECINT runs with a stopwatch. Or perhaps
you can come with some more automatable means, but you should aim to take
before/after timestamps from *outside* the HVM guest, since you're trying to
ascertain whether the HVM timekeeping is screwed on your system.
-- Keir
next prev parent reply other threads:[~2007-08-14 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 10:37 Xen Benchmarking guidelines Nick L. Petroni Jr.
2007-08-14 10:53 ` Keir Fraser [this message]
2007-08-14 11:31 ` Nick L. Petroni Jr.
2007-08-15 15:20 ` Nick L. Petroni Jr.
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=C2E74840.1429C%keir@xensource.com \
--to=keir@xensource.com \
--cc=mwh@cs.umd.edu \
--cc=npetroni@cs.umd.edu \
--cc=xen-devel@lists.xensource.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 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.