Edrock200

Some good reference info:
 
https://gist.github.com/0xbadfca11/da0598e47dd643d933dc
and here:
https://charbelnemnom.com/2016/01/how-to-recover-data-on-refs-volume-between-different-windows-server-2016-technical-preview-builds-refs-ws2016-hyperv/

Fwiw I ran into this problem too when seeding my drive with Google drive sync. 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. This causes constant requests to the same chunks, eventually causing throttling then disconnects.
 
 
If your seeding method works the same way you can try my fix. I changed the cache mode from fixed to proportional and left it at 50/50 so the temp chunks could stay in read cache. 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. Prefetch was unusable.
 
After changing it barely reads during seeding and prefetch works. The only time I get slow downs are when my disk I/o on cache drive can't keep up, but generally only lasts a few seconds but doesn't cause disconnects. Here's my settings:
 
50tb clouddrive encrypted
80gb proportional cache 50/50
10 dl threads
5 ul threads
Prefetch trigger 5mb
Prefetch fwd 50mb (have tested UpTo 200mb w/o issue but found anything over 50 didn't increase overall avg read speed during burst transfers). Get steady ~15-20MB (150-200mbs) read speed on burst transfer downloads with these settings. Have gig connection but upload throttled to 350 and dl to 250mbs. Unlocking these throttles did not increase download speeds with prefetch set higher. Uploads would surge to 550+ then get throttled by Google regardless of thread count.
Time window 30 seconds
Upload chunk 20mb
Download size 5mb (anything larger caused disconnect/throttling issues and slow performance, and lower would cause the same issues due to clouddrive thread count surge when it tries to catch up)
Chunk cache size 100mb
Provider Google drive
Drive indexing disabled
Antivirus scans disabled on drive
 
Not sure if drive pool will support, but if your using encryption for each drive you may want to make your drives decrypted, add to drive pool, then use bitlocker to encrypt drive pool drive so your CPU isn't doing multiple encryption/decryption cycles against the same data. I would also disable read striping until your seeding is complete to prevent a download thread surge.

BTW, apologies if my earlier post sounded harsh - that was definitely not my intent, and I know it's a small team of 2 managing everything.
 
If I can recollect on my problems - it was all fine and dandy when I upgraded to the release version (0.870). The issue started to kick in between Builds 870-880. I'm not entirely sure if the break was server led (I'm using Google Drive BTW). 
 
But I can confirm that the issue is solved when I re-created the drive w/ the release version. My old drive was created way back in the early beta builds.
 
And kudos to a great product: I've been an early beta user and it's amazing to see how polished this product has become. Looking forward to the product's deeper integration with Drivepool.

Hey all,
I've run into an odd issue with CloudDrive and PreFetch. Essentially, with prefetch off, I get 300MB/s up and ~150MB/s down (when something is being pushed/pulled.) when I turn prefetch on, the upload downloads come to a screeching halt, uploads bob up and down from 0 to 15mb's and downloads generally stay under 1mb/s although they may occasionally go up to 8mb/s for a few seconds. Once I turn prefetch off and the time expires, the numbers spike back to their normal throughput. Here are my settings:
 
Google Drive attached
256TB AES Encrypted mount
10TB in use
20MB chunks
10MB/1 minute upload trigger
500/500 Internet with Gig-E link
Upload/download threads set to 5/5 (have tried 3/3 and 10/10 as well with same results.) Background I/O checked
Prefetch - Trigger 1MB, Forward 400MB, Time 1800 Seconds (tried 10/100/600, 1/1000/3600 with same results)
Upload Download limited to 250MB/250MB, although tried removing these limits for testing, same results
30GB expandable cache set on local SSD drive (tried increasing, reducing, changing to fixed or dynamic with same results)
Upload queues are at 0 prior to prefetch being enabled, but once enabled they start to grow due to the speed decrease
 
One thing I've noticed, I'f I'm understanding the summary screen correctly, is above the upload and download arrows it will show numbers like 3x or 5x. I'm assuming this is the number of threads being utilized. With prefetch off, this number never exceeds my max i/o settings for upload/download. However, with prefetch turned on, the download threads will go up, I've seen it go up to 12x for example. Does prefetch not respect the max i/o settings or am I missing something? Also, the prefetch fills slowly. Is the prefetch duration saying "if 1mb of same file is read, fetch next 400MB steadily/evenly spread over the next 1800 seconds" or is it saying "if 1mb of same file is read, fetch next 400MB as fast as possible keep for 1800 seconds."?
 
Also, what is the significance of the "Background I/O" checkbox next to upload threads? What does turning this option off and on do?
Thanks in advance,
-Ed

Mystery solved. I had installed netdrive and mounted my Google drive, but didn't use it to copy anything to/from drive. My a/v scanner is configured to scan local and net drives, and it began attempting to scan repeatedly. Apparently Google didn't like this. I contacted them after they unlocked the account and figured it out. All is well. Sorry for the false flag.
 
I like the idea of sharing the drive though to prevent getting locked out. I own my domain and gsuite account. I bought it and have 6 accounts paid for monthly (6 family members, we each pay $10/mo). I have about 20tb of system backups, system images, photos, multimedia and my iTunes library. On a side note, the latest version of cloudrive allows me to use prefetch now w/o causing disconnects or throttling.

Just had my google drive account disabled, only thing on it was cloud drive. Anyone else have this happen?

Setting is only changeable when attaching or creating drives, it's "minimum download size". It can't be set higher then cache chunk size.

Wow I didn't know that! Was contemplating buying another one or two cloud drive licenses, this makes the decision much easier.  
 
Side note to the OP. To work around the one-pc|one drive limitation, I installed "sync thing" on my nodes. It is free and works sort of like a dropbox or google drive client but without the central cloud storage piece, all data syncs and resides solely between your equipment. So I can sync directly between nodes, or even do one way syncs, exclude files, etc. It's very customizable.