A distributed load-balancing policy for a multicomputer
Software—Practice & Experience
Low cost management of replicated data in fault-tolerant distributed systems
ACM Transactions on Computer Systems (TOCS)
The ITC distributed file system: principles and design
Proceedings of the tenth ACM symposium on Operating systems principles
A distributed file service based on optimistic concurrency control
Proceedings of the tenth ACM symposium on Operating systems principles
Consistency and recovery control for replicated files
Proceedings of the tenth ACM symposium on Operating systems principles
Sacrificing serializability to attain high availability of data in an unreliable network
PODS '82 Proceedings of the 1st ACM SIGACT-SIGMOD symposium on Principles of database systems
A client-based transaction system to maintain data integrity
SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles
Converting a swap-based system to do paging in an architecture lacking page-referenced bits
SOSP '81 Proceedings of the eighth ACM symposium on Operating systems principles
The TRIPOS filing machine, a front end to a file server
SOSP '83 Proceedings of the ninth ACM symposium on Operating systems principles
ACM SIGOPS Operating Systems Review
| Hi-index | 0.00 |
A network file system called Multifile is described. It meets response, availability, and stability requirements as primitive functions. Multifile has a high degree of responsiveness because its component parts compete among themselves to service file requests; it has high availability because it maintains multiple copies of files; and it exhibits stable behavior over wise range of system parameters. The responsiveness of Multifile to read requests improves as the number of pages per request rises, implying that read ahead pages can profitably be cached at client sites. The throughput of Multifile improves as the request size increases and as the number of clients increases. As server load increases, the responsiveness of Multifile to read requests is stable in most configurations. The throughput of writes is unstable as the number of pages in the wire request rises, implying that write back pages should not be cached at client sites. The scale of events in file service is dominated by disk activity, so lost message exceptions do not occur frequently enough to affect file service; however, duplicate message exceptions are a factor in performance.