From: xuehai zhang <hai@cs.uchicago.edu>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Xen-devel@lists.xensource.com
Subject: Re: New MPI benchmark performance results (update)
Date: Tue, 03 May 2005 17:05:50 -0500 [thread overview]
Message-ID: <4277F5BE.5040706@cs.uchicago.edu> (raw)
In-Reply-To: <4277DE0E.9010905@us.ibm.com>
Hi Nivedita,
Thanks for the response and the suggestion!
>> Hi all,
>>
>> In the following post I sent in early April
>> (http://lists.xensource.com/archives/html/xen-devel/2005-04/msg00091.html),
>
>
>
> Hi, thanks for sharing the data - it was interesting.
> I tried to find additional data on the benchmarks using
> the link you have for the user manual but it gave me
> a 404 Error.
I corrected the link error and now you can access the user manual through the link.
> It wasn't clear whether your benchmarks
> use TCP or UDP or possibly raw sockets?
I've read through the PMB user manual and it doesn't mention the communication protocol it uses.
However, I do read "typically TCP/IP is the protocol used over Ethernet networks for MPI
communications" from several references.
> As has been pointed out by several people, running the
> 2.6 kernel and comparing apples to apples as much as possible
> would help.
I fully agree with that and currently I try to rerun the experiments by using the same kernel
versions for both dom0 and domU (maybe native linux too).
>
> Is there any chance you kept some of the system statistics
> and settings (netstat -s, sysctl -a info)?.
I did not collect them while running the benchmarks, but I will try to log them when I rerun the
experiments.
> Did you tune the settings for the system at all?
No, I did not do any specific things to tune the system.
>> Alltoall latency (max domU/linux > 60). The performance difference in
>> the last example is HUGE and we could not think about a reasonable
>> explaination why transferring 512B message size is so much different
>> than other sizes. We appreciate if you can provide your insight to
>> such a big performance problem in these benchmarks.
>
>
> You have an anomalous point on most of the results - and again,
> knowing what kind of traffic this is would really help.
I will try to dig into the source code and find it out.
Thanks again for the help.
Xuehai
>
> thanks,
> Nivedita
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-05-03 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 9:11 New MPI benchmark performance results (update) xuehai zhang
2005-05-03 9:28 ` Steven Hand
2005-05-03 16:36 ` xuehai zhang
2005-05-03 16:13 ` Mark Williamson
2005-05-03 16:58 ` xuehai zhang
2005-05-03 20:24 ` Nivedita Singhvi
2005-05-03 22:05 ` xuehai zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 13:56 Ian Pratt
2005-05-03 16:48 ` xuehai zhang
2005-05-03 19:09 Santos, Jose Renato G (Jose Renato Santos)
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=4277F5BE.5040706@cs.uchicago.edu \
--to=hai@cs.uchicago.edu \
--cc=Xen-devel@lists.xensource.com \
--cc=niv@us.ibm.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.