All of lore.kernel.org
 help / color / mirror / Atom feed
From: xuehai zhang <hai@cs.uchicago.edu>
To: "Santos, Jose Renato G (Jose Renato Santos)" <joserenato.santos@hp.com>
Cc: "Turner, Yoshio" <yoshio_turner@hp.com>,
	Aravind Menon <aravind.menon@epfl.ch>,
	Xen-devel@lists.xensource.com,
	G John Janakiraman <john@arivalai.hpl.hp.com>
Subject: Re: MPI benchmark performance gap between native linux anddomU
Date: Tue, 05 Apr 2005 00:27:22 -0500	[thread overview]
Message-ID: <425221BA.5030801@cs.uchicago.edu> (raw)
In-Reply-To: <6C21311CEE34E049B74CC0EF339464B902FB1E@cacexc12.americas.cpqcorp.net>

Jose,

Thank you so much for your valueable information.

>   I guess I overlooked the rates you reported in your post.
>   Looking now at your rates carefully I got somewhat confused. When you
> say MB/sec do you mean Megabyte/sec or Migabit/sec? 

It is Megabyte/sec (2^20 bytes)

> In any case these
> are much lower rates than in our case (we were using a gigabit network).
> Now, I am starting to think that your problem might be different than
> ours, but it does not hurt to try changing the advertised window, just
> in case.

I will try your suggestion and sent out update tomorrow morning.

>   Also, the numbers your report are inconsistent. You mention that your
> network is 10 MB/s, and that native linux achieve 14.9 MB/s. How is it
> possible to achieve a throughput higher than the network bandwidth?
> Could you please clarify?

Yes, it is a little confusing. It is due to the caculation of SendRecv's throughput. If you take a 
look at the PMB user manual (following the link in my previous email), the throughput is defined as 
2X/1.048567/time (time is latency). So, it is a weighted throughput and could go beyond 10MB/s, 
which is the max bandwidth of the network.

Thanks.

Xuehai

  reply	other threads:[~2005-04-05  5:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05  3:10 MPI benchmark performance gap between native linux anddomU Santos, Jose Renato G (Jose Renato Santos)
2005-04-05  5:27 ` xuehai zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-06  7:23 Ian Pratt
2005-04-06  7:08 Ian Pratt
2005-04-06  0:37 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06  4:24 ` xuehai zhang
2005-04-06  0:17 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 23:59 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 15:23 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 15:47 ` Keir Fraser
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-04 23:30 Ian Pratt
2005-04-04 23:43 ` xuehai zhang
2005-04-05 22:29   ` xuehai zhang
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

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=425221BA.5030801@cs.uchicago.edu \
    --to=hai@cs.uchicago.edu \
    --cc=Xen-devel@lists.xensource.com \
    --cc=aravind.menon@epfl.ch \
    --cc=john@arivalai.hpl.hp.com \
    --cc=joserenato.santos@hp.com \
    --cc=yoshio_turner@hp.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.