All of lore.kernel.org
 help / color / mirror / Atom feed
From: kuas <ku4s@users.sourceforge.net>
To: xen-devel-ml <xen-devel@lists.sourceforge.net>
Subject: Hyperthreading network benchmark
Date: Sat, 30 Oct 2004 21:32:25 -0400	[thread overview]
Message-ID: <418440A9.4030307@users.sourceforge.net> (raw)

Hi all,

I found enabling hyperthreading for Xen (the hypervisor layer) would 
degrade network performance. I wonder if the synchronization cost of Xen 
(the hypervisor) running on multi cores/multiprocessors environment is 
high (around 30 %). The benchmark I did is against Intel Pentium 2.4 MHz 
Hyperthreaded CPU and Gigabit network (ethernet and switch). I was using 
WebStone 2.5 benchmark against Apache 2.0.50-1.0 (FC1 httpd package).  I 
was also running 2.4.27 for the domains kernel. The result I have:
1. Native:
    a. Hyperthread enabled: 370 Mb/sec
    b. Hyperthread disabled: 270-290 Mb/sec
2. Domain 0 has the same performance around: 270 Mb/sec
3. Domain 1:
    a, Hyperthreaded enabled, domain1 run on different core: 175-185 Mb/sec
    b. Hyperthreaded disabled or even if enabled domain 1 is forced to 
be in the same Core with domain 0: 255-265 Mb/sec

Please note, I was only sending request to one domain at a time. It 
seems when the two domain ran in the same core we had higher 
performance. I wonder if any other people has done almost similar test 
and have similiar/opposite behavior. Are these behaviors make sense?

Thanks in advance for any comments.

Kuas.




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

             reply	other threads:[~2004-10-31  1:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31  1:32 kuas [this message]
2004-10-31  1:46 ` Hyperthreading network benchmark Kip Macy
2004-11-01 22:56   ` Adam Heath
2004-10-31  2:05 ` Mark A. Williamson

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=418440A9.4030307@users.sourceforge.net \
    --to=ku4s@users.sourceforge.net \
    --cc=xen-devel@lists.sourceforge.net \
    /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.