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

note

Browse source
This commit is contained in:
Joey Hess 2021-09-22 11:10:55 -04:00
parent 798b33ba3d
commit 44d3d50785
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/todo/bwlimit.mdwn
View file

@ -12,3 +12,20 @@ works, it will probably work to put the delay in there. --[[Joey]]
> Implmentation in progress in the `bwlimit` branch. Seems to work, but see > Implmentation in progress in the `bwlimit` branch. Seems to work, but see
> commit message for what still needs to be done. --[[Joey]] > commit message for what still needs to be done. --[[Joey]]
> The directory special remote, when resuming an interrupted
> transfer, has to hash the file (with default annex.verify settings),
> and that hashing updates the progress bar, and so the bwlimit can kick
> in and slow down that initial hashing, before any data copying begins.
> This seems perhaps ok; if you've bwlimited a directory special
> remote you're wanting to limit disk IO. Only reason it might not be ok
> is if the intent is to limit IO to the disk containing the directory
> special remote, but not the one containing the annex repo.
>
> Other remotes, including git over ssh, when resuming don't have that
> problem. Looks like chunked special remotes narrowly avoid it, just
> because their implementation choose to not do incremental verification
> when resuming. It might be worthwhile to differentiate between progress
> updates for incremental verification setup and for actual transfers, and
> only rate limit the latter, just to avoid fragility in the code.
> --[[Joey]]