Bowsa

I don't know how to fix this. But If I'm supposed to be using the Cloud Drive (through Google) as a "normal" drive, it always behaves erratically. I've mentioned it a few times here, but the software will not even BEGIN uploading until the very last byte has been written to the local cache. So for example, if I'm uploading 7 videos, and they all total 100GB, even with 99GB in the queue to upload, it won't even upload until that last gig is written to the local cache. This is frustrating because it causes two problems: error messages and wasted time. The first big issue is the constant barrage of notifications that "there's trouble connecting to the provider" or downloading, or uploading, but it doesn't even upload! A consequence of these constant error messages is that the drive unmounts because of these messages triggering the software to disconnect. So unless I'm babying my computer, I can't leave the files transferring as normal (which means not pressing the pause upload button). The other issue is the waste of time. Instead of uploading what's currently in the local cache and subsequently deleting that queue, it waits for EVERYTHING to write to the local cache. Settings: UL/DL Threads = 10 Upload Threshold: 1 MB or 5 Minutes Error Message(s): I/O error: Cloud Drive Cloud Drive (D:\) is having trouble uploading data to Google Drive. This operated is being retired. Error: SQLite error cannot rollback - no transaction is active This error has occurred 2 times. Make sure that you are connected to the internet and have sufficient bandwidth available. I/O error Cloud drive Cloud Drive (D:) is having trouble uploading data to Google Drive in a timely manner. Error: Thread was being aborted. This error has occured 2 times. This error can be caused by having insufficient bandwidth or bandwidth trhottling. Your data will be cached locally if this persists. If these two problems are fixed, this software would be perfect. Now I've recommended this program many times because when you're monitoring it works beautifully. But the only thing missing is rectifying these issues so it actually behaves like a normal drive that doesn't constantly throw up errors.

So that's what I'm trying to figure out. What exactly is causing the bottle-neck from my NVME Drive to the NVME Local Cache, is it the decryption? I'm really happy with the product, but if I could get higher transfer speeds I'd be extremely happy

Yes. This is my workflow Downloader program (Downloads + Unpacks) ---> Other program flags download, and begins transferring to Cloud Drive This process is from NVME to NVME, so there should be no bottlenecks caused by the drive itself. Also I do have the trigger set to 10 minutes, but if the program is displaying that 10GB are ready to upload, that should've activated the upload trigger long before the 5 minutes lapsed. For now I've had to do it manually..I pause the upload, and wait for the file to "upload" and/or transfer to the Local cache, and then I enable uploading which works. I also use 10 threads upload/download, but I've noticed that not disabling uploading and letting it handle on its own works.. eventually but then I get errors about the drive not uploading/downloading in time; although harmless, they're a bit annoying to see.

Yes, My transfer speeds remain unchanged between all builds to date

There we go. I just don't understand..chunks don't begin uploading until the entire file is copied. So if a 15GB file is being transferred, and 7 GB are already in the local cache and ready to upload, it won't begin uploading until the entire file is in the local cache. Also the transfer rates make absolutely no sense to me. I know it can't be my NVME causing the slowness, but I have my i7-7700k OC'd to 4.8 GHz, and that should be good for the encryption and splitting of files right?

Local Cache Size 10GB+ | Expandable | NVME | 250GB Free out of 500GB | 100 MB RAM Cache

I'm having trouble understanding this.. I have an NVME with insane read/write speeds, but when I copy a file to the Cloud Drive it's my understanding that the following happens: File gets copied to local cache File must be copied in its entirety for anything else to happen File then gets encrypted/broken into chunks File gets uploaded? I'm not sure if these are the correct order of steps But if the first step is the case, and I'm copying a file to the local cache first..why is it so slow? The transfer rate is 30 MBs from my disk to local cache..but my NVME is 3200 MB/s Read, 1900 MB/s Write..so what gives? What possible justification is there for this slow transfer speed if it's not even uploading yet.

Hey I was wondering if this would be a good idea and/if it would work? Two Google Drive Accounts One 16TB Cloud Drive on Account One and another 16TB Cloud Drive on Account Two Pool them together through DrivePool = 32 TB Shared Data Would this result in the following? Saving/uploading a file to this Aggregate Cloud Drive Pool would use the software's Drive Balancing to Distribute files in their entirety (Video File 1 - with it's various chunks on Drive One --- Video File 2 - with it's various chunks on Drive Two) or would it upload 50% of the chunks from Video file 1 to Drive 1 and the other 50% to Drive 2? My Goal is to have a distributed Cloud DrivePool not simply for increased storage, but the effective doubling of my Upload Cap for the day 1,500 GB Daily vs 750, along with doubling my API calls/reliability? Would this be a good option? That way if there's a file playing from Drive A, and another from Drive B simultaneously I can avoid throttling by not having so many download requests in a short time? Reason being that if I have 10 Download threads enable (to avoid DDOS protection) and I use two separate drives (or more likely 1 drive and multiple file/chunk-group request) on the same provider, would it be slower or more straining on the download requests? My idea sounds great in theory, but I wanted confirmation to see if the software would work this way?

But my problem is the download portion

Anyone know how to fix?

Provider: Legit.EDU Google Drive Hey, guys, I don't know what's going on with StableBit cloud, but it's been an absolute nightmare to use. I first started uploading a substantial amount of data on the 26th of February, was able to download/prefetch at 150 Mbps+, but then I got throttled in uploading. Sometime in the evening of the following day, the limits on my uploading were released and I would get full speed when uploading data. But I've been patiently waiting for this mysterious API/Bandwidth cap to be released and nothing. It's been a few days since my initial upload and it seems like a useless drive. Low size files (20-30gb) somehow kinda work when it's downloading even with a lot of failures and retries, but playing a 4K file is impossible. Every once in a while (with no activity) I check the cloud drive and I see that it needs to be authorized, or the bandwidth is throttled or any other problem. I can't even detach the drive because it says "access denied". I can't do anything, I was wondering if maybe it has to do with my account itself? Maybe it could be a problem with my account itself? Would purchasing a Google suites account alleviate this issue, and is there a way to transfer my drive there?