Timeline for NFSv3 vs NFSv4 performance drop
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2023 at 17:46 | history | edited | ron | CC BY-SA 4.0 | added 1743 characters in body |
| Sep 11, 2023 at 17:08 | comment | added | Kamil | Thank you for such detailed explanation! I tried to explain myself more clearly and added a paragraph in my first post. | |
| Sep 11, 2023 at 15:01 | comment | added | ron | NFS v4 worked toward a fix for this problem by evolving to a stateful protocol, which enabled data caching on clients with the delegations feature. But this surface fix ended up creating new problems below since the rest of the NFS v4 architecture wasn’t updated to leverage this change. Trips between the client and the NFS server actually increased from 5-6 to around 10. As a result, in spite of the ability to now cache data, this overly chatty design worsened performance and scalability from NFS v3 to NFS v4. NFS v4.2 finally sets things right with its Compound Operations feature. | |
| Sep 11, 2023 at 15:00 | comment | added | ron | datacenterknowledge.com/industry-perspectives/… ... NFS v4.2, solves a number of v4 performance issues and also introduces many new features. | |
| Sep 11, 2023 at 14:56 | history | answered | ron | CC BY-SA 4.0 |