From: alekcejk@googlemail.com
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: Re: Re: Re: limited network bandwidth with 3.2.x kernels
Date: Wed, 22 Feb 2012 03:26:19 +0200 [thread overview]
Message-ID: <6857224.s9gmvGgyqq@localhost.localdomain> (raw)
In-Reply-To: <1329845484.18384.20.camel@edumazet-laptop>
В сообщении от Вторник 21 февраля 2012 18:31:24 вы написали:
> > But maximum speed in 3.1.10 kernel (without this sysctl settings) still
> > a bit more than in 3.2.7 - 11 MB/s instead of 10.3 MB/s.
> >
> > --2012-02-21 18:56:36-- ftp://ftp3.de.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/8.2/FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz
> > 100%[======================================>] 2 066 424 512 11,0M/s in 3m 30s
> > 2012-02-21 19:13:55 (9,39 MB/s) - «/dev/null» saved [2066424512]
>
> Thats one measure, you'll have to make a lot of different measures to
> make this significant, preferably in a lab to rule out different
> external network conditions.
So, I did a couple of download tests from ftp3.de.freebsd.org with kernel 3.1.10.
Here traffic plot for net.ipv4.tcp_rmem="4096 87380 897664":
http://img848.imageshack.us/img848/2425/net897664.png
Here plot for net.ipv4.tcp_rmem="4096 87380 4127616":
http://img14.imageshack.us/img14/311/net4127616.png
And comparison of both plots:
http://img684.imageshack.us/img684/7163/netoh.png
The main notable difference is that with 4127616 there is
never stright line (when wget shows 11 M/s ) as with 897664.
Speed with 4127616 is close to 11 M/s but never constant.
I was able to reproduce this at least 3 times.
next prev parent reply other threads:[~2012-02-22 1:27 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:04 limited network bandwidth with 3.2.x kernels alekcejk
2012-02-13 20:18 ` Eric Dumazet
2012-02-13 21:13 ` Eric Dumazet
2012-02-13 21:58 ` alekcejk
2012-02-13 22:44 ` Eric Dumazet
2012-02-13 22:51 ` Neal Cardwell
2012-02-13 23:09 ` alekcejk
2012-02-13 23:14 ` Eric Dumazet
2012-02-13 23:24 ` alekcejk
2012-02-13 23:49 ` alekcejk
2012-02-14 3:06 ` Neal Cardwell
2012-02-14 3:26 ` alekcejk
2012-02-14 5:55 ` Eric Dumazet
2012-02-14 14:09 ` alekcejk
2012-02-13 21:16 ` alekcejk
2012-02-21 4:21 ` alekcejk
2012-02-21 16:45 ` Eric Dumazet
2012-02-21 17:19 ` alekcejk
2012-02-21 17:31 ` Eric Dumazet
2012-02-21 18:53 ` alekcejk
2012-02-22 1:26 ` alekcejk [this message]
[not found] ` <1920135.kl3o7Tt79c@localhost.localdomain>
[not found] ` <1329228798.4818.0.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2012-02-14 14:28 ` alekcejk
2012-02-14 16:00 ` Eric Dumazet
2012-02-14 16:43 ` alekcejk
2012-02-15 4:43 ` Eric Dumazet
2012-02-15 6:03 ` Neal Cardwell
2012-02-15 6:06 ` Eric Dumazet
2012-02-15 7:52 ` Bill Fink
2012-02-15 8:00 ` Eric Dumazet
2012-02-15 8:18 ` Bill Fink
2012-02-15 8:31 ` Eric Dumazet
2012-02-15 13:44 ` alekcejk
2012-02-15 13:43 ` Re: Re: Re: Re: " alekcejk
2012-02-15 13:44 ` alekcejk
2012-02-15 13:49 ` Eric Dumazet
2012-02-15 13:53 ` Eric Dumazet
2012-02-15 14:11 ` alekcejk
2012-02-15 14:49 ` Neal Cardwell
2012-02-15 14:56 ` Eric Dumazet
2012-02-15 15:05 ` alekcejk
2012-02-15 15:08 ` Eric Dumazet
2012-02-15 19:44 ` Neal Cardwell
2012-02-16 7:29 ` Eric Dumazet
2012-02-16 13:40 ` Eric Dumazet
2012-02-16 13:51 ` Ben Hutchings
2012-02-16 15:09 ` Eric Dumazet
2012-02-16 16:37 ` Ben Hutchings
2012-02-16 17:01 ` David Miller
2012-02-16 17:22 ` Neal Cardwell
2012-02-16 17:54 ` alekcejk
2012-02-16 18:19 ` Neal Cardwell
2012-02-16 21:49 ` alekcejk
2012-02-16 21:59 ` Eric Dumazet
2012-02-16 22:08 ` alekcejk
2012-02-16 22:35 ` Eric Dumazet
2012-02-17 16:41 ` Neal Cardwell
2012-02-21 18:41 ` Eric Dumazet
2012-02-21 19:11 ` David Miller
2012-02-22 5:51 ` Neal Cardwell
2012-02-22 7:36 ` Eric Dumazet
2012-02-23 18:39 ` Neal Cardwell
2012-02-23 18:49 ` Eric Dumazet
2012-02-27 19:39 ` David Miller
2012-02-17 16:55 ` Re: " Neal Cardwell
2012-02-16 18:22 ` Eric Dumazet
2012-02-16 19:44 ` Eric Dumazet
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=6857224.s9gmvGgyqq@localhost.localdomain \
--to=alekcejk@googlemail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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.