> > 2.2.4 Adding sufficient memory at satellite uplink router
> > can fix problem
> >
> > * I've heard several mentions (not on this list) that if
> > you make your windows big enough and add a lot of
> > memory at the uplink, throughput problems can be
> > overcome.
>
> Yep, this is a hole that I had pegged as being there later on,
> but this is a good place to add such a discussion (also); This one
> needs to be couched with the proper qualifications as to where,
> when and why this will help.
>
> I'm actually going to place the discussion in with the top
> misconception. Again, thanks!
>
You need to add the memory at the bottleneck router, which is not
necessarily the uplink router if the satellite link is not bottleneck.
(But the adminstrator of the bottleneck router may have no connection
with the adminstrator of the satellite link, so this is a problematic
approach to solving this problem.)
I would also like to point out that if the satellite link is slow
enough to be the bottleneck, then it is probably slow enough so that
TCP works just fine over it with little need for improvement.
If the satellite link is fast enough to make large window extension
relevant (and in which case there may be some risk that the slow-start
probing may prematurely overrun the queue before bottleneck link)
then the bottleneck link is likely *not* at the satellite uplink, but
somewhere else in the Internet.
-Tim Shepard
BBN Systems and Technologies
[email protected]
+1 617 873 2013
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:29 EST