In my continued efforts to get the first SEED out, with the combination of all the drives I have as well as my lack of upload speed, first, thanks to Chris (config/settings) and the rest of the community (settings) and I think the latest release (algorithm changes?), at this time, instead of getting ALL of my Google Drives needing to be reauthorized, I get one every say...week or so. That is VERY happy!
I was again looking through the options of the CloudDrive software, as I am still waiting on ~100GB of data to be uploaded (a LOT of it in cache at this time).
As I wait for the feature request to be implemented (I'm being patient, really!) - where you can set a GLOBAL upload thread limit or at least potentially get a ROUND robin style upload (work one provider / drive, process some amount of data, then move on to the next - which I would HOPE will provide more targeted bandwidth instead of fracturing my meager upload speed (5mbps/50mbps cable modem) into nothingness as I get overtaken by overhead).
Regardless, I noticed that under Technical Details, located next to the drive selection pulldown there is a checkbox for allowing "writing to this drive". As this has been running for over a week and I do not want to bugger anything up, I thought I would ask what this does.
If I go through ALL my drives and UNSELECT this, will this put the processing of the drives in a paused state? This would allow me to go through one at a time enabling this. Let that one drive finish, move on to the next, etc. Then, once the seeding is done, enable all drives and let it manage things as it needs. Backups shall not be very large as it will be differences (~20-50 MB at a time, vs the 177GB I'm seeding with).
Does this sound like a reasonable action? Or is this an abuse of a troubleshooting tool that will hose things?
Just as a reminder, I have 20 Cloud Drives. Using BOX, Google Drive (not Enterprise Drive), Dropbox. Before the latest release I also had Mediafire in there.
Those drives are pooled together using Drivepool.
As I understand it, DrivePool is happy as the cache is taking up the slack. From CloudDrive's perspective, it is trying to upload as fast as it can across EVERY drive, which I think at this point, my drives are tolerant enough (again, thanks to the settings from the community), but I think the overhead of hitting EVERY drive is slowing things to a crawl. If we had the global threading, I would just set that to 1 - 3 to start with. As we do not, I'm trying to see if that checkbox will give me this option at least to finish up this initial seeding.
Thanks again to everyone for their help!