Minimising disk usage via TorrentDataOpener about torrent

[anacrolix]

Yes, this is supported. I have just this use case myself, and the client can redownload pieces that go missing. I use a LRU cache, and recently fixed a bug when the cache is smaller than a file being downloaded.

Storing data in S3 for example, will also work. However you may want to optimize reads from the storage to reuse open streams or add your own caching layer due to the high connect and open latency on S3. Writes to storage do not lock the client, but will reduce the throughout from peers if they're slow.

1. Should be fine. Has been done. Trimming is handled correctly.
2. See above. Also writes in middle of cloud files depends on your API.
3. Easiest solution.

[jpillora]

Awesome, thanks for the info! Will start with 3 and see how I go from there.