Thank you for the fast reply! I am still in the conception phase, so I don't have a command line - I am trying to understand the system first.
First of all, thank you for confirming this is possible. I actually want to have the opposite for my other usecase.
What I am trying to do: I want to store my less popular torrent content on an encrypted Google drive and seed it long term. Judging from your answer I would assume that each requested piece makes an API Call to google and I would quickly get banned. I am actually doing it at the moment on my local computer with Google Filestream and get 403 banned by google multiple times per week.
What I came up with, was using the cache back end an set a very high limit for cache size like:
RCLONE_CACHE_CHUNK_TOTAL_SIZE = 1500G
This way I would create very little API Calls with google but only if the whole file was downloaded as soon as the first piece is requested and not all the pieces individually. Or at least the requests should be way bigger then the average piece size to download multiple pieces at once.
Can I control the minimum "request" size? So let's say that the server downloads at least 16 MB, even if just 1 MB of the file is requested by the torrent application? (Is that what RCLONE_CACHE_CHUNK_SIZE does?)
Is this chunk size always aligned at the start of the file?
Let's assume that I set it to 8 MB and now the torrent client tries to read the part between 14–15MB of an uncached file. Will rclone download (and store in cache?) the part
A) 14–15 MB
B) 8–16 MB
C) 14-22 MB
D) The whole file?
(as counted from the start of the file)
Thank you very much in advance!