Steve Francis wrote:
Just as a head up - this sort of below should not be done on things
like web servers that support lots of concurrent connections - you'll
eat all your memory for sockets.
Unless you have something like FreeBSD´s auto-tuning inflight window
stuff which
would allow large wi
Just as a head up - this sort of below should not be done on things like
web servers that support lots of concurrent connections - you'll eat all
your memory for sockets.
Marshall Eubanks wrote:
On Tue, 30 Sep 2003 15:44:03 -0400
"Temkin, David" <[EMAIL PROTECTED]> wrote:
Is there anyone in
Marshall Eubanks wrote:
On Tue, 30 Sep 2003 15:44:03 -0400
"Temkin, David" <[EMAIL PROTECTED]> wrote:
Is there anyone in a production environment who, as part of their system
build process, adjusts the TCP receive window/MSS/etc. on production
systems?
As a concrete data point:
the tuning
On Tue, 30 Sep 2003 15:44:03 -0400
"Temkin, David" <[EMAIL PROTECTED]> wrote:
> Is there anyone in a production environment who, as part of their system
> build process, adjusts the TCP receive window/MSS/etc. on production
> systems?
>
Look at
http://www.internet2.edu/~shalunov/writing/tcp-pe
Hi, Dave.
] Is there anyone in a production environment who, as part of their system
] build process, adjusts the TCP receive window/MSS/etc. on production
] systems?
Increasing it helps, particularly if both ends have the same
setting. Don't forget to enable both RFC1323 and RFC2018 support
if
We do on some systems that do bulk data transfer over links with latency
(latency being 70 ms cross country).
Temkin, David wrote:
Is there anyone in a production environment who, as part of their
system build process, adjusts the TCP receive window/MSS/etc. on
production systems?
I'm dealing
Title: Adjusting TCP windows on production systems?
Is there anyone in a production environment who, as part of their system build process, adjusts the TCP receive window/MSS/etc. on production systems?
I'm dealing with a few latency issues and the MSS settings improve them, but I'
