Re: Internal TCP/IP send buffer?

• Previous message: Arkady Frenkel: "Re: How to check if NIC operates half or fullduplex mode?"
• In reply to: Arkady Frenkel: "Re: Internal TCP/IP send buffer?"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 24 Oct 2004 15:57:42 +0200

Additionally look at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;214397
The size now , article talk about 8K ( as it was in W9x/NT ), but 17K (
17,520 ) in W2K/XP for ethernet > 1 Mbps and it's change to 64K ( as you
wrote ) by
Autodetermination for lan of 100 Mbps and more.
That really great adaptative feature of modern MS TCP stack to change !

Arkady

"Arkady Frenkel" <arkadyf@hotmailxdotxcom> wrote in message
news:eflNMuTuEHA.2596@TK2MSFTNGP15.phx.gbl...
> Just look at
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwxp/html/
> comperfnetapppt1.asp
> Arkady
>
> "Marton Anka" <marton@03am.com> wrote in message
> news:e8CCHxFuEHA.3860@TK2MSFTNGP09.phx.gbl...
> > Alun,
> >
> > Thanks for the reply.
> >
> > > Here's the first clue - any time you talk about disabling Nagle, you
> have
> > > to wonder if TCP is the right protocol for you.
> >
> > No - Nagle can be both a blessing and a curse. That's why there's an
> option
> > to disable it. It's simply there to help with bandwidth efficiency when
> > throughput is preferred over latency. In this case I need to minimize
> > latency.
> >
> > > Probably the TCP window negotiated between client and server on
> > > connection. You shouldn't do anything to work around this, it's a
> valuable
> > > property of TCP.
> >
> > I'm not trying to work around them. If the buffer I'm talking about is
> > indeed the TCP window, then how do I go about adjusting its size for the
> > current connection?
> >
> > >> Can this internal buffer be disabled or limited in size somehow?
> > >
> > > That will not solve your problem. Your problem is that you are asking
> for
> > > TCP to be made to behave like UDP. It would be better to use UDP
> instead.
> >
> > Actually, it will solve my problem. If you can show me where UDP
> guarantees
> > delivery, orders packets and controls data flow then yes, it would be
> better
> > to use it. At this point however it seems like I'm asking for this
> > non-existent UDP to behave more like TCP. So I might as well use TCP the
> way
> > it was intended to be used, but how can I control that pesky buffer?
> >
> > To describe the situation:
> >
> > Client is connected to Proxy over the internet, possibly with a very
slow
> > connection. Server is connected to Proxy over gigabit ethernet. Server
is
> > sending small chunks of data to Proxy that gets forwarded to Client. TCP
> > buffering between Proxy and Server is causing problems with the data
being
> > out of date by the time it is recv()-d by Proxy. Proxy has no knowledge
of
> > the protocol used between Client and Server, and even if it did it could
> not
> > do anything with it as the data is encrypted.
> >
> > Thanks,
> >
> > Marton
> >
> >
>
>

• Previous message: Arkady Frenkel: "Re: How to check if NIC operates half or fullduplex mode?"
• In reply to: Arkady Frenkel: "Re: Internal TCP/IP send buffer?"
• Messages sorted by: [ date ] [ thread ]