Poul-Henning Kamp writes:
> In message <[EMAIL PROTECTED]>, John Hay write
> s:
>
> >> Try disabling newreno in both ends:
> >>
> >> sysctl -w net.inet.tcp.newreno=0
> >>
> >> On my laptop with Wavelan cards this increases TCP throughput by a
> >> factor of 5.
> >
> >Yes, that mak
In message <[EMAIL PROTECTED]>, John Hay write
s:
>> Try disabling newreno in both ends:
>>
>> sysctl -w net.inet.tcp.newreno=0
>>
>> On my laptop with Wavelan cards this increases TCP throughput by a
>> factor of 5.
>
>Yes, that makes a HUGE difference. I only did it on the current box.
>
> >>
> >>I've tested last nights make release built
> >> install via both ftp and nfs and am seeing
> >> some rather strange results timeing wise:
> >>
> >>A full install (ie: select ALL) w/ ports.
> >>
> >>NFS: about 18 minutes. (ave. about 1000KB/sec)
> >>
> >>FTP: about 70
In message <[EMAIL PROTECTED]>, John Hay write
s:
>>
>>I've tested last nights make release built
>> install via both ftp and nfs and am seeing
>> some rather strange results timeing wise:
>>
>>A full install (ie: select ALL) w/ ports.
>>
>>NFS: about 18 minutes. (ave. about 1000KB
> Hi,
>
>I've tested last nights make release built
> install via both ftp and nfs and am seeing
> some rather strange results timeing wise:
>
>A full install (ie: select ALL) w/ ports.
>
>NFS: about 18 minutes. (ave. about 1000KB/sec)
>
>FTP: about 70 minutes. (ave. about 45
Hi,
I've tested last nights make release built
install via both ftp and nfs and am seeing
some rather strange results timeing wise:
A full install (ie: select ALL) w/ ports.
NFS: about 18 minutes. (ave. about 1000KB/sec)
FTP: about 70 minutes. (ave. about 45KB/sec)
on the sam