mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2018-08-02 13:15:59 -04:00
parent 05e573e672
commit 184cae8172
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/tips/local_caching_of_annexed_files/comment_4_42906e52528907a0960ab8b08c2eedd4._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2018-08-02T16:58:45Z"
content="""
Parallel downloads will use the cache repository for everything if it has a
lower cost than other repositories. That's why the cost is set to 10 in the
example. If it has the same cost as another repository, parallel downloads
will spread the load between them. (This also means you can have multiple
caches with the same cost and distribute load amoung them..)
You should never be pulling from the cache repo, so there should be nothing
to merge from it. That's what the remote.cache.annex-pull is there to prevent
git-annex sync doing, but you also have to avoid pulling from it yourself.
Using tunables with the cache does seem to work. Since all remotes usually
have the same tunables as the local repo, there could potentially be
bugs (or optimisations?) where it applies the local tunables to the
remote, but in a little testing it seemed to work.
"""]]