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

move todo item to right place; reply

Browse source
This commit is contained in:
Joey Hess 2012-09-13 17:44:37 -04:00
parent ecb9d52770
commit f417f7153f
2 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/design/assistant/syncing.mdwn
View file

@ -41,6 +41,7 @@ all the other git clones, at both the git level and the key/value level.
to a remote, so it won't be uploading content to us.) Note: Does not to a remote, so it won't be uploading content to us.) Note: Does not
need to use the TransferScanner, if we get and check a list of the changed need to use the TransferScanner, if we get and check a list of the changed
files. files.
* [[use multiple transfer slots|todo/Slow_transfer_for_a_lot_of_small_files.]]
## data syncing ## data syncing

9
doc/Slow_transfer_for_a_lot_of_small_files..mdwn → doc/todo/Slow_transfer_for_a_lot_of_small_files..mdwn
View file

@ -8,4 +8,13 @@ But currently it seems like git-annex is only using one thread to transfer(per h
An option to select number of transfer threads to use(possibly per host) would be very nice. An option to select number of transfer threads to use(possibly per host) would be very nice.
> Opening a lot of connections to a single host is probably not desirable.
>
> I do want to do something to allow slow hosts to not hold up transfers to
> other hosts, which might involve running multiple queued transfers at
> once. The webapp already allows the user to force a given transfer to
> happen immediately. --[[Joey]]
And maybe also an option to limit how long a queue the browser should show, it can become quite resource intensive with a long queue. And maybe also an option to limit how long a queue the browser should show, it can become quite resource intensive with a long queue.
> The queue is limited to 20 items for this reason. --[[Joey]]