Dajinn

My best guess is that the cache must constantly be talking to the cloud drive and telling it what's there. Nothing else really makes sense.

One thing that is puzzling is I'm just not sure why the outbound data is so much. No one has been using Plex yet so it's not like there are any streams going outbound. Another thing I did to try to circumvent the library scanning phase was I successfully migrated my Plex metadata folder from my local server up into this VPS. And today I've already used 84 GB of outbound bandwidth. Just wish I could have some sort of idea what it was...

Version 1.0.1.880 The size is 256 TB (but I'm only using 13 TB) I created the drive on a local machine I physically own a while back. For google drive: 10 / 10 20mb chunk size 100mb minimum download size

Hey guys, I have a LeaseWeb Virtual Server that I provisioned (XL spec to be specific), however, I am already worried as I have begun to let my libraries scan Google Drive (which is provisioned through CloudDrive) and noticed that my outbound bandwidth is already at 500~ GB used. My plan with LeaseWeb grants me 10TB of traffic which should be enough but I am really confused as to how I've used 500 GB of OUTBOUND data according to their charts. The Plex server itself should be reading (aka downloading) from the drive and creating its metadata locally, right? Any ideas as to how I could have consumed 500GB of outbound traffic already? Is this something to do with Cloud Drive? Thanks!