From: Jacob Gorm Hansen <jacobg@diku.dk>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: First result from small address spaces
Date: Tue, 26 Apr 2005 16:58:53 -0700 [thread overview]
Message-ID: <426ED5BD.6010709@diku.dk> (raw)
hi,
I finally have a setup where I can measure I/O performance of stock vs.
my own 'small address spaces' enabled version of Xen.
Doing a simple iperf -w256K with the client in domU and the server on a
remote machine, everything without hyper-threading and using bridged
networking.
Stock xen : 574MBits/s
SAS xen: 620MBits/s
Not massive, but an 8% improvement in this one case. I suspect that in
general, this only makes a real difference if the domU doing something
useful with the CPU other than feeding data into a socket.
Where can I adjust the thresholds for buffering of packets and interrupts?
Jacob
reply other threads:[~2005-04-26 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=426ED5BD.6010709@diku.dk \
--to=jacobg@diku.dk \
--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.