From: Nivedita Singhvi <niv@us.ibm.com>
To: Cherie Cheung <ccyxen@gmail.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-devel] Network performance - sending from VM to VM using TCP
Date: Wed, 25 May 2005 16:24:13 -0700 [thread overview]
Message-ID: <4295091D.10505@us.ibm.com> (raw)
In-Reply-To: <4713f859050525152448a0f609@mail.gmail.com>
Cherie Cheung wrote:
> Hi,
>
> I have been simulating a network using dummynet and evaluating it
I haven't played with dummynet and don't know if there are
additional issues inherent in using dummynet itself...
> using netperf. Xen3.0-unstable is used and the VMs are
> vmlinuz-2.6.11-xenU. The simulated link is 300Mbps with 80ms RTT.
> Using netperf, I sent data using TCP from domain-0 of machine 1 to
> domain-0 of machine 2. Then I repeat the experiment, but this time
> from VM-1 of machine 1 to VM-1 of machine 2.
>
> However, the performance across the two VMs is substantially worse
> than that across domain-0. Here's the result:
>
> FROM VM to VM:
> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to dw10.ucsd.edu
> (172.19.222.210) port 0 AF_INET
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^6bits/sec
>
> 87380 65536 65536 80.28 24.83
Your send message size is exactly your socket size. It is also
the size of the default write buffer. The kernel uses half the
buffer (very roughly) for data
Were you testing with 65536 bytes exactly for some reason?
This is stop and go traffic and normally the kernel doesn't
use the entire buffer to store data - it's roughly half...
Could you test with different send sizes?
> FROM domain-0 to domain-0:
> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to damp.ucsd.edu
> (137.110.222.236) port 0 AF_INET
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^6bits/sec
>
> 87380 65536 65536 80.11 280.62
>
> Here's the setting of the network buffer:
>
> net.core.wmem_max = 8388608
> net.core.rmem_max = 8388608
> net.ipv4.tcp_bic = 1
> net.ipv4.tcp_rmem = 4096 87380 8388608
> net.ipv4.tcp_wmem = 4096 65536 8388608
>
> Does anyone know why the performance across two VMs is so bad? Any fix
> to it? Thank you.
If you just want to improve your peformance, increase your
buffer sizes!
For example:
tcp_rmem = 4096 1398080 8388608
tcp_wmem = 4096 1398080 8388608
Were you seeing losses, queue overflows?
More importantly, how much memory do you have in the system and
how were you allocating it?
thanks,
Nivedita
next prev parent reply other threads:[~2005-05-25 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 22:24 Network performance - sending from VM to VM using TCP Cherie Cheung
2005-05-25 23:04 ` Kip Macy
2005-05-25 23:24 ` Nivedita Singhvi [this message]
2005-05-26 5:28 ` [Xen-devel] " Cherie Cheung
2005-05-27 0:05 ` Nivedita Singhvi
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=4295091D.10505@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ccyxen@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.