public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: John Bradford <john@grabjohn.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	davem@redhat.com, ahu@ds9a.nl, linux-kernel@vger.kernel.org
Subject: Re: problems achieving decent throughput with latency.
Date: Mon, 03 Feb 2003 10:03:48 -0800	[thread overview]
Message-ID: <3E3EAF04.9010308@candelatech.com> (raw)
In-Reply-To: <200302031611.h13GBl9D019119@darkstar.example.net>

John Bradford wrote:
>>>TCP can only send into a pipe as fast as it can see the
>>>ACKs coming back.  That is how TCP clocks its sending rate,
>>>and latency thus affects that.
>>
>>Wouldn't you just need larger windows?  The problem is latency, not 
>>bandwidth.
> 
> 
> Exactly - the original post says that no problems are experienced
> using UDP, which backs that up.

I started poking around, and found the tcp_mem, tcp_rmem, and tcp_wmem
tunables in /proc/sys/net/ipv4...

If I change the values, I see up to 25Mbps with 25ms of latency.
It would go higher, but I have uncovered a performance bug in my code that
drops a packet every now and then at those higher rates, so that backs tcp
off quickly.  I should have that fixed this evening and will continue testing.


Here are the values that I used.  The documentation I found is not overly
descriptive, so if anyone has any suggestions for improving my tunings, please
let me know!

Also, if it's as simple as allocating a few more buffers for tcp, maybe we
should consider defaulting to higher in the normal kernel?  (I'm not suggesting
**my** numbers..)

# See the kernel documentation: Documentation/networking/ip-sysctl.txt
my $tcp_rmem_min     = 4096;
my $tcp_rmem_default = 256000;  # TCP specific receive memory pool size.
my $tcp_rmem_max     = 3000000;  # TCP specific receive memory pool size.

my $tcp_wmem_min     = 4096;
my $tcp_wmem_default = 256000;  # TCP specific receive memory pool size.
my $tcp_wmem_max     = 3000000;  # TCP specific receive memory pool size.

my $tcp_mem_lo       = 20000000; # Below here there is no memory pressure.
my $tcp_mem_pressure = 30000000; # Can use up to 30MB for TCP buffers.
my $tcp_mem_high     = 30000000; # Can use up to 30MB for TCP buffers.




> 
> John.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  parent reply	other threads:[~2003-02-03 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02  7:38 problems achieving decent throughput with latency Ben Greear
2003-02-02 11:48 ` bert hubert
2003-02-03  5:14   ` David S. Miller
2003-02-03 15:37     ` Chris Friesen
2003-02-03 16:11       ` John Bradford
2003-02-03 16:19         ` bert hubert
2003-02-03 18:03         ` Ben Greear [this message]
2003-02-03 19:18           ` Eric Weigle
2003-02-04  5:19           ` David S. Miller
2003-02-04  7:50             ` Ben Greear
2003-02-04  7:39               ` David S. Miller
2003-02-04  8:42                 ` Ben Greear
2003-02-04  8:41                   ` David S. Miller
2003-02-04  8:51                   ` Ben Greear

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=3E3EAF04.9010308@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ahu@ds9a.nl \
    --cc=cfriesen@nortelnetworks.com \
    --cc=davem@redhat.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox