> protocol itself. The problem is it forces the server and client to > synchronise on every read/write syscall, which results in terrible > bandwidth utilisation. Unless we see some remarkable improvements in [...] > > I'm sure I've missed something, but readahead is safe for all these > constructs except event files, where if you readahead (and get data) > but the client closes the file before actually read()-ing the buffered
unfortunately, client caching is problematic. the open research question is, how to make latency the domain of the file server(s) and not of the application. - erik
