This commit is contained in:
parent
8d3fe19bc6
commit
f25ba0099b
1 changed files with 7 additions and 0 deletions
7
doc/forum/Will_git-annex_solve_my_problem__63__.mdwn
Normal file
7
doc/forum/Will_git-annex_solve_my_problem__63__.mdwn
Normal file
|
@ -0,0 +1,7 @@
|
|||
Here's my current situation:
|
||||
|
||||
I have a box which creates about a dozen files periodically. All files add up to about 1GB in size. The files are text and sorted. I then rsync the files to n servers. The rsync diff algorithm transfers way less than n * 1GB because the files are largely the same. However, this distribution technique is inefficient because I must run n rsync processes in parallel and the rsync diff algorithm takes a lot of CPU.
|
||||
|
||||
How could I use git-annex instead of rsync?
|
||||
|
||||
Because the box producing the new files also has the old files, then presumably git could calculate the diffs for each file once instead of n times as with the rsync solution? Then only the diffs need be distributed to the n servers... using git-annex? And finally the newly updated version of the dozen files needs to be available on each of the n servers. Ideally, the diffs would not mount up over time on either the publishing server or the n servers, thus causing out of disk problems etc. How to deploy git-annex to solve my problem?
|
Loading…
Reference in a new issue