3 ms·
Totally disagree. You have to understand how NFS caching effects your application and what kind of performance and security/availability you need. At that point
by romeisendcoming 8y ago
Totally disagree. You have to understand how NFS caching effects your application and what kind of performance and security/availability you need. At that point you can make NFS work for you. You also have to make good decisions about how you implement. This type of use case (long open file waits with concurrent access) are a nightmare with any shared filesystem. Most approaches dealing with possibly stale content are shoulder shrugs.
- jabl 8y ago> This type of use case (long open file waits with concurrent access) are a nightmare with any shared filesystem. Most approaches dealing with possibly stale content are shoulder shrugs. Well, it is possible to handle correctly, e.g. Lustre. Lustre, however, is very complex compared to NFS, so there's absolutely a price to be paid. NFS implements close-to-open consistency, which is much weaker than full cache coherency (again, e.g. Lustre).
- romeisendcoming 8y agoYou want a network shared filesystem then design your data for it.