Re: [9front] cfs, aan and network recommendations

[sirjofri <sirjofri+ml-9front@sirjofri.de>]

17.11.2021 10:45:00 hiro <23hiro@gmail.com>:

> i *assumed* that the version would be a local copy!

The version itself is the local copy, saved on the cache partition. Cfs 
uses the qid.version field to determine if the version is outdated or 
not.

So it still needs to ask the server for the version of the file. If it's 
out of date, it fetches the new version and responds with data from that. 
If the qid.version didn't change, it answers with the data from the file 
directly. That's why latency is important.

However, when reading static files like pdfs and images (big filesize to 
protocol ratio) it's really a benefit.

Imagine a process with many big files where only few of them change, and 
the result of the process is quite small and written back to the file 
server, cfs should be quite good. Only those few changed files have to be 
transferred while the other big files remain the same on the cfs cache 
partition. The process does it magic calculation based on the cached 
data, and writes the small artifact back to the (original) server.

sirjofri