First time posting here, I'm sorry if I didn't set up the post correctly.
The title basically summarizes my question. I want to use RClone to seed torrents from the cloud. The problem is, lots of random access requests and latency will just wreck performance and I'd probably hit API hit rate limits and get my account locked our or suspended.
So what I'd like to do instead is, whenever a peer connects, the entire contents of the torrent is downloaded and fully cached on my local machine before seeding begins, then after no peer has connected for 24 hrs let's say, the cache is flushed. I have gigabit internet so it would never take more than a few minutes to fully cache a torrent before seeding starts. And of course I'd need to have a large enough cache so I don't run out. This would only be used for old torrents on a private tracker that hardly ever get downloaded. Is this at all possible to do, and how would I go about setting it up? What flags would I have to use? Would it work with any torrent client?
Alternatively, what would be even better is, as soon as a peer requests a torrent, RClone starts locally caching it and then the torrent client starts uploading immediately at a slower speed than the caching/download speed and only serves the peer(s) chunks that have already been cached locally. So it's real-time caching+uploading. That way the peer wouldn't have to wait for the whole torrent to cache (although again, with gigabit internet it doesn't really matter). But I'm thinking, for this method to work, the torrent client would have to know how to implement it, and right now none do is my guess.
This has to be possible somehow with RClone, right? At least the former option with full caching before seeding.
Any advice would be greatly appreciated!