From: xuehai zhang <hai@cs.uchicago.edu>
To: xuehai zhang <hai@cs.uchicago.edu>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, Xen-devel@lists.xensource.com
Subject: Re: MPI benchmark performance gap between native linux anddomU
Date: Tue, 05 Apr 2005 17:29:33 -0500 [thread overview]
Message-ID: <4253114D.4050800@cs.uchicago.edu> (raw)
In-Reply-To: <4251D10C.4040508@cs.uchicago.edu>
xuehai zhang wrote:
> Ian,
>
> Thanks for the quick response! Explainations to your comments are inline
> below.
>
>>> I did the following experiments to explore the MPI application
>>> execution performance on both native linux machines and inside of
>>> unpriviledged Xen user domains. I use 8 machines with identical HW
>>> configurations (498.756 MHz dual CPU, 512MB memory, on a 10MB/sec
>>> LAN) and I use Pallas MPI Benchmarks (PMB).
>>
>>
>>
>>> The expreiment results show, running a same MPI benchmark in user
>>> domains usually results in a worse (sometimes very bad) performance
>>> comparing with on native linux machines. The following are the
>>> results for PMB SendRecv benchmark for both experiments (table1 and
>>> table2 report throughput and latency respectively). As you may
>>> notice, SendRecv can achieve a 14.9MB/sec throughput on native linux
>>> machines but can get a maximum 7.07 MB/sec throughput if running
>>> inside of user domains. The latency results also have big gap.
>>
>>
>>
>>> I will appreciate your help if you had the similar experience and
>>> wanna share your insights.
>>
>>
>>
>> Xen (or any kind of virtualization) is not particularly well suited to
>> MPI type applications, at least unless you're using Inifiniband or some
>> other smart NIC that avoids having to use dom0 to do the IO
>> virtualization.
>>
>> However, the results you are seeing are lower than I'd expect.
>>
>> Are you running dom0 and the domU on the same CPU or different CPUs. How
>> does changing this effect the results?
>
>
> I did not specify "cpu" option in Xen's configuration file, so I think
> both dom0 and domU run on the same CPU (1st CPU). I will try to assign
> them to different CPUs later.
I think I said something wrong here. If I do not specify "cpu" option in Xen config file, I observe
Xen usually assigns the 2nd CPU to domU while running dom0 on the 1st CPU.
>> Also, are you sure the MTU is the same in all cases?
>
>
> The outputs of "ifconfig" show MTU is 1500 in all cases.
>
>> Further, please can you repeat the experiements with just a dom0 running
>> on each node.
>
>
> I will do it and update you later.
>
> Thanks again for the help.
>
> Xuehai
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-04-05 22:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 23:30 MPI benchmark performance gap between native linux anddomU Ian Pratt
2005-04-04 23:43 ` xuehai zhang
2005-04-05 22:29 ` xuehai zhang [this message]
2005-04-05 22:34 ` Mark Williamson
2005-04-05 22:39 ` xuehai zhang
2005-04-05 22:43 ` Mark Williamson
2005-04-06 4:25 ` xuehai zhang
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 2:07 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 8:59 ` Keir Fraser
2005-04-05 22:22 ` Nivedita Singhvi
2005-04-05 22:23 ` xuehai zhang
2005-04-05 22:34 ` xuehai zhang
2005-04-05 22:53 ` Nivedita Singhvi
2005-04-05 22:58 ` Nivedita Singhvi
2005-04-05 3:10 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 5:27 ` xuehai zhang
2005-04-05 15:23 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 15:47 ` Keir Fraser
2005-04-05 23:59 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 0:17 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 0:37 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 4:24 ` xuehai zhang
2005-04-06 7:08 Ian Pratt
2005-04-06 7:23 Ian Pratt
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=4253114D.4050800@cs.uchicago.edu \
--to=hai@cs.uchicago.edu \
--cc=Xen-devel@lists.xensource.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
/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.