xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Marco Tizzoni <elibus@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Sending packet at fixed rate really bad performance
Date: Mon, 28 Sep 2009 10:17:31 -0400	[thread overview]
Message-ID: <20090928141731.GA7107@phenom.dumpdata.com> (raw)
In-Reply-To: <f9611b0f0909271026r2a91187fl71ed8673a5ca22d9@mail.gmail.com>

On Sun, Sep 27, 2009 at 07:26:49PM +0200, Marco Tizzoni wrote:
> 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.

Lets narrow this down a bit.  You are comparing two different systems
with potentially different interfaces. Lets concentrate on one machine
first. Is the performance on your Athlon 64 without Xen (meaning you
boot without Xen) in the same ball-park figure?

I want to make sure we can eliminate the hardware being at fault here.

  reply	other threads:[~2009-09-28 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 17:26 Sending packet at fixed rate really bad performance Marco Tizzoni
2009-09-28 14:17 ` Konrad Rzeszutek Wilk [this message]
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=20090928141731.GA7107@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=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).