UrlStore documentation of cache behavoir (when combining with MFS)
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
Hey guys there's currently very little documentation available about the experimental function "UrlStore".
I understand that there's no local data cached while adding the file to IPFS, rather a link is pointing to an URL where the data is fetched on demand.
I like to combine this feature with MFS for easy altering of the file/folder structure, while the HTTP server still holds the data.
The response time of a `ipfs files cp` of a CID stored with UrlStore suggests, that the MFS lazy-mounts the new CID to the local MFS and not pulls the content to the local cache.
The question arises if the `--nocopy` flag is a general 'no local caching' flag, or if my local cache will start caching the files when they are requested from the IPFS because I've added it to the MFS. While the inclusion of the CID in the MFS will hinder any garbage collection attempts of those files from the cache, basically resulting in a rising cache usage until my local storage is used up (http server holds like 2 magnitudes more storage than I have locally).
Best regards
Ruben
Contributor guide
Assessment
This issue has not been assessed yet.