Yeah... We have that as well, but I put strict limits on how many readers are allowed on any NFS data source. With well organized reads, even a single machine can cause serious load on an ordinary NFS server. I have had very bad experiences where lots of maps read from a single source; the worst was when a bunch of map functions all initialized themselves from a single mySQL server which promptly went fairly catatonic.
On 12/20/07 8:30 PM, "Joydeep Sen Sarma" <[EMAIL PROTECTED]> wrote: > the nice thing is that if we do ever fall behind (network glitches, filer > overload, whatever) - the code automatically increases the number of readers > to catch up (with certain bounds on number of concurrent readers).
