3 ms·
AWS's [docs on EFS performance](https://docs.aws.amazon.com/efs/latest/ug/performance-tips.html#efs-perf-nfs-client-mnt-settings https://docs.aws.amazon.com/efs
by jitl 6mo ago
AWS's [docs on EFS performance](https://docs.aws.amazon.com/efs/latest/ug/performance-tips.html#efs-perf-nfs-client-mnt-settings https://docs.aws.amazon.com/efs/latest/ug/performance-tips.h...) say:
> Don't use the following mount options:
> - fsc – This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies.
If the S3 Files sync logic ran client-side, we could almost entirely avoid file access latency for cached files and paying for new expensive EFS disks. I already pay for a lot of NVMe disks, let me just use those!
- MontyCarloHall 6mo ago>This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies. That's true for any NFS setup, not just EFS. The benefit of local NFS caching is to speed up reads of large, immutable files, where latency is relatively negligible. I'm not sure why AWS specifically dissuades users from enabling caching, since it's not like bandwidth to an EFS volume is even in the ballpark of EBS/NVMe bandwidth.