summaryrefslogtreecommitdiff
path: root/Assistant/ScanRemotes.hs
Commit message (Collapse)AuthorAge
* where indentationGravatar Joey Hess2012-10-31
|
* split ScanRemotes and liftedGravatar Joey Hess2012-10-29
|
* scan multiple remotes in one passGravatar Joey Hess2012-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | The expensive transfer scan now scans a whole set of remotes in one pass. So at startup, or when network comes up, it will run only once. Note that this can result in transfers from/to higher cost remotes being queued before other transfers of other content from/to lower cost remotes. Before, low cost remotes were scanned first and all their transfers came first. When multiple transfers are queued for a key, the lower cost ones are still queued first. However, this could result in transfers from slow remotes running for a long time while transfers of other data from faster remotes waits. I expect to make the transfer queue smarter about ordering and/or make it allow multiple transfers at a time, which should eliminate this annoyance. (Also, it was already possible to get into that situation, for example if the network was up, lots of transfers from slow remotes might be queued, and then a disk is mounted and its faster transfers have to wait.) Also note that this means I don't need to improve the code in Assistant.Sync that currently checks if any of the reconnected remotes have diverged, and if so, queues scans of all of them. That had been very innefficient, but now doesn't matter.
* fix priority inversionGravatar Joey Hess2012-08-24
| | | | low cost ==> high priority
* run full transfer scan on all remotes at startupGravatar Joey Hess2012-08-24
| | | | Or when a remote first becomes available after startup.
* make higher priorities and full scans be preserved when addingGravatar Joey Hess2012-08-24
|
* keep logs of failed transfers, and requeue them when doing a non-full scanGravatar Joey Hess2012-08-23
| | | | of a remote
* scan cheapest remotes firstGravatar Joey Hess2012-08-23
| | | | This way, we get transfers from cheapest remotes.
* fix crash when just one remote needs to be scannedGravatar Joey Hess2012-08-05
| | | | | | | | | The TMVar is supposed to be left empty once the map is empty, but the code neglected to do that, so the next time takeMVar got an empty map, which is not handled since that was supposed to never happen.. Also, avoid any possibility of this crash. If an empty map somehow creeps in, just retry.
* add TransferScanner threadGravatar Joey Hess2012-07-22
Efficiently finding transfers that need to be done to get two repos back in sync seems like an interesting problem.