Prefetch was unusable.Īfter changing it barely reads during seeding and prefetch works. Before I did this my downloads were constantly at least 50% of my upload speeds even though I don't have verify chunks on nor was I doing any reads against the drive, and eventually disconnects. I changed the cache mode from fixed to proportional and left it at 50/50 so the temp chunks could stay in read cache. If your seeding method works the same way you can try my fix. This causes constant requests to the same chunks, eventually causing throttling then disconnects. What I found was Google drive writes temp files to a hidden directory on the same drive your seeding, then copies them over when complete. If needed, I'll certainly submit for a feature request on this one.įwiw I ran into this problem too when seeding my drive with Google drive sync. For me, I am using this as a backup, so performance is NOT high on my list and due to the advanced caching, even while the drives are 'waiting' to finish dumping, I can seemingly continue to run my backup every day and the Clouddrive just seems to be able to handle the differences - all the while trying to catch up with the filled up cache. Since my home network is slower than most on here (5/50), I do not think I'll run into issues such as listed above. I realize this will KILL my performance overall - however it will keep the drives just happily dumping their cache to the drives in the cloud. Until then, instead of having to re-authorize my Google Drive or other drives once a day (as the pool continues to seed), can I setup a global threads limit for upload? This way all other drives will just have to wait their turn, instead of splitting down to <100kbps each, then erroring out due to 'slow' speeds.

Along with this, is there a way to setup a round robin of sorts? I have been working to overcome some strange lagginess and believe that through my testing that lag will go away once I have finished seeding my drivepool (made from Clouddrive drives).

Google drive upload slow