From: Marco Tizzoni <elibus@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Sending packet at fixed rate really bad performance
Date: Sun, 27 Sep 2009 19:26:49 +0200 [thread overview]
Message-ID: <f9611b0f0909271026r2a91187fl71ed8673a5ca22d9@mail.gmail.com> (raw)
Hi all,
I'm doing some tests about i/o performance and cpu overhead in dom0.
I've coded a small tool that can sends UDP packets at fixed rate or
flood. While sending packet at fixed rate I'm experiencing performance
problem, related to how Xen handle signal, I guess.
On my laptop (Core2 duo P8700), with no Xen running, I can send
packets at a rate of 20k, 40k, 60k, 80k/s achieving an actual packet
rate per second pretty near to the requested rate.
On Xen (dom0 with no guest running and no load - Athlon 64 dual core
4000+ ), the performance are really bad.
Here what happen:
Requested | Actual
10 | 10.03
100 | 100.05
200 | 200.04
500 | 250.04
1000 | 250.18
10000 | 247.49
20000 | 250.26
40000 | 250.24
It seems impossibile to go over 250 packets/second, but in flood
configuration (send packet as fast as possible) the actual rate is
quite higher, 39k packets/second about.
The main difference is in the code. Flood loop as been implemented like this:
------------------
for (;;)
send_pkt();
------------------
while the fixed rate use setitimer to wake up send_pkt() when needed.
Any idea of why this happen?
bye,
Marco
next reply other threads:[~2009-09-27 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 17:26 Marco Tizzoni [this message]
2009-09-28 14:17 ` Sending packet at fixed rate really bad performance Konrad Rzeszutek Wilk
2009-09-28 16:28 ` Marco Tizzoni
2009-09-28 16:44 ` Konrad Rzeszutek Wilk
2009-09-28 18:00 ` Marco Tizzoni
[not found] <4d6de31b0912301058j1dea3f2fud656822d29025266@mail.gmail.com>
2010-01-25 12:15 ` Richard Brady
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=f9611b0f0909271026r2a91187fl71ed8673a5ca22d9@mail.gmail.com \
--to=elibus@gmail.com \
--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 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).