Michael Eischer 6f53ecc1ae adapt workers based on whether an operation is CPU or IO-bound ... Use runtime.GOMAXPROCS(0) as worker count for CPU-bound tasks, repo.Connections() for IO-bound task and a combination if a task can be both. Streaming packs is treated as IO-bound as adding more worker cannot provide a speedup. Typical IO-bound tasks are download / uploading / deleting files. Decoding / Encoding / Verifying are usually CPU-bound. Several tasks are a combination of both, e.g. for combined download and decode functions. In the latter case add both limits together. As the backends have their own concurrency limits restic still won't download more than repo.Connections() files in parallel, but the additional workers can decode already downloaded data in parallel.		2022-07-03 12:19:26 +02:00
..
testdata
checker.go	adapt workers based on whether an operation is CPU or IO-bound	2022-07-03 12:19:26 +02:00
checker_test.go	repository: Rework blob saving to use an async pack uploader	2022-07-02 22:42:34 +02:00
testing.go	copy: Load snapshots before indexes	2022-04-09 12:27:25 +02:00