In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> * John Polstra <[EMAIL PROTECTED]> [010831 15:03] wrote:
> > FreeBSD's "src/etc/amd.map" file still has "vers=2,proto=udp". Do
> > you think we should change it?
>
> I'm not familiar with amd, what implications would
In various performance tests we have found proto=tcp to be uniformly
a Good Thing. I'd vote for that to be default in general, but
perhaps there is an AMD-specific reason for UDP; I can't imagine
what that would be, though.
--ckg
On Fri, Aug 31, 2001 at 01:03:46PM -0700, John Polstra wrote:
> I
* John Polstra <[EMAIL PROTECTED]> [010831 15:03] wrote:
> In article <[EMAIL PROTECTED]>,
> Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> >
> > Using UDP is usually a bad idea, I would use tcp, I find that these
> > flags make for a decent mount point that's quite fast:
> > rw,tcp,intr,nfsv3,
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>
> Using UDP is usually a bad idea, I would use tcp, I find that these
> flags make for a decent mount point that's quite fast:
> rw,tcp,intr,nfsv3,-w=32768,-r=32768
FreeBSD's "src/etc/amd.map" file still has "vers=2
* Steve Shorter <[EMAIL PROTECTED]> [010831 12:14] wrote:
> Howdy!
>
> I am interested in tuning UDP for NFS over a 100Mbs LAN.
>
> Specifically, to tune UDP, what are guidelines/restrictions for
> setting the sysclt variables
>
&g
< said:
> net.inet.udp.maxdgram
> net.inet.udp.recvspace
> I assume that increasing both of these will improve performance.
Neither of these have any impact on UDP performance. In fact, there
really are no UDP performance parameters to be tweaked; the UDP
protocol doesn't hav
Howdy!
I am interested in tuning UDP for NFS over a 100Mbs LAN.
Specifically, to tune UDP, what are guidelines/restrictions for
setting the sysclt variables
net.inet.udp.maxdgram
net.inet.udp.recvspace
I assume that increasing both of these
