SunOS 4 used to have a NFS mount mount option nocto (no close to open
consistency checking) that would suppress getting fresh attributes
when opening a file. IMHO it is ok to enable this option on
filesystems that never change (or atleast rarely). I always used it
when mounting /usr on diskless s
Thanks for comments so far.
It looks like the best solution for me is going to be to boot diskless into
a ramdisk. It's been quite a job finding out how to do that; there doesn't
seem to be much in the way of documentation.
Reverse-engineering the source suggests that the following methods exist
On Sat, 27 Apr 2002, Brian Candler wrote:
> > If you are really
> > into clusters with low-latency, you might want to look into something like
> > NFS V4 (Is anybody working on that on FreeBSD, anymore?), AFS, CODA, or
> > something more specialized. Those networked filesystems have a
> > bidre
On Fri, 26 Apr 2002, Brian Candler wrote:
> I have been tracing some performance problems on diskless systems. In
> particular, the following test program:
>
>perl -e 'for ($i=0;$i<1000;$i++) { open F,"; close F;}'
>
> generates 1000 'access' transactions, and hence an exchange of 2000 UDP
On Fri, Apr 26, 2002 at 04:42:48PM -0700, Andrew P. Lentvorski wrote:
> > ... Could it safely be made less restrictive, e.g. don't
> > clear the cache when opening a file for read?
>
> In a word, no. Why couldn't the sysadmin be running "make installworld"
> on the NFS server while you're runnin
On Fri, 26 Apr 2002, Brian Candler wrote:
>perl -e 'for ($i=0;$i<1000;$i++) { open F,"; close F;}'
I will assume that you wrote this *only* to prove the point. However, if
you are using NFS, you need to check the status of both open *and* close.
Otherwise you are likely to start breeding *v
* Brian Candler <[EMAIL PROTECTED]> [020426 10:15] wrote:
>
> Now, there is obviously some "consistency" issue to beware of. Are there any
> NFS gurus out there who can say why it is necessary to clear the attribute
> cache on _every_ open? Could it safely be made less restrictive, e.g. don't
> c
I have been tracing some performance problems on diskless systems. In
particular, the following test program:
perl -e 'for ($i=0;$i<1000;$i++) { open F,"; close F;}'
generates 1000 'access' transactions, and hence an exchange of 2000 UDP
packets, just from repeatedly opening the same file.
A
