All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: "Apparao, Padmashree K" <padmashree.k.apparao@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: httperf  throughput
Date: Thu, 21 Sep 2006 12:01:33 -0700	[thread overview]
Message-ID: <4512E18D.3050305@us.ibm.com> (raw)
In-Reply-To: <B5677069E3D9994D9EE1C7295072EA960B063A72@orsmsx402.amr.corp.intel.com>

Apparao, Padmashree K wrote:
> Hi,

> I am running apache and httperf on the latest Xen unstable.

> When I have the webserver running in a single cpu guest I can barely get
> 720 Mbps over 2 nics (each 1 Gb). That is the throughput is about 36% of
> the native linux throughput. (I get line rate on native linux with the
> cpu being fully utilized). The guest cpu is 100% utilized while dom0 is
> about 80% utilized.
> 
>  
> 
> Said another way, I can get 2000 connections per second in Xen before
> the cpu chokes while in Linux I get about 7000 connections per sec. Is
> this what is expected. 
> 
>  
> 
> Does anyone have similar/alternate performance data to share?
> 
> Thanks
> 
> -          Padma

Padma,

The degradation from native for Xen guests will vary considerably
with workload.  There have not been too many network-intensive
workloads run yet, possibly because that's the least optimized
so far, although of late a lot of Herbert Xu's work has made
quite a difference.

How many procs in the box, and are you pinning the vcpus?
What are the parameters you are running with for httpperf?

I'd still recommend netperf over ttcp, which some of the other
people running tests are using, but I don't have any numbers.

Could you profile your benchmark runs and share the data? Would
be very interesting. Also, a little more information on the
system (memory, etc).


thanks,
Nivedita

      reply	other threads:[~2006-09-21 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  4:49 httperf throughput Apparao, Padmashree K
2006-09-21 19:01 ` Nivedita Singhvi [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=4512E18D.3050305@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=padmashree.k.apparao@intel.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 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.