Curtis Villamizar wrote:
>
> In message <[email protected]>, matthew halsey writes:
> > Aaron, Mark et al
> >
> > In addition, if it is not there already, we could add a graph/table showing
> > max possible throughput for a variety of window sizes with some markers of
> > where typical TCP stacks place their windows.
> > E.g. I think Microsoft adopts 8kByte window => max thruput = 8192 x 8 / 0.6s
> > = 109 kbps.
> > Sun = ?
> > FTP = ?
> >
> > What do you think?
> >
> > Matt
>
> To provide decent service over satellite both ends need to have a
> large buffer configured. BSD defaults to 16KB but it is typically
> settable to 256KB without changing a constant in the kernel. Then it
> can be set to up to 2GB.
>
> To what extent is sending a single TCP flow at high speed an issue in
> non-military applications? Keeping a remote web cache synched, bulk
> smtp relay transfer, and bulk nntp transfer can all be configured to
> use large windows if the pair is known to have a sat link between.
>
> The applications that do need high speed single flows just have to
> increase window size in the application using setsockopt. A host that
> is dangling off a seatellite link can also change the default window
> size in the kernel to something more appropriate.
>
> I suppose Windoze and NT users are out of luck.
sort of.
regedit Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP
and set DefaultRcvWindow = 65536
Windoze95 sat/ip (l)users are much happier with this (I am, anyway).
M$TCP defaults to 8192.
-brad
>
> Curtis
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:31 EST