thatvalis
-
Posts
10 -
Joined
-
Last visited
-
Days Won
1
Posts posted by thatvalis
-
-
No.
The chunk size is akin to the sector size on the disk. Without reformatting the disk, it's not really possible. The same is true here.
Even if there *was*, it would require us to download and re-upload the data *anyways*.
Drive Options -> Performance -> I/O Performance.
Increase the number of download threads. This should increase the number of simultaneous connections that StableBit CloudDrive uses. Don't set this too high or Google will aggressively throttle the connections, which will cause the same sort of issue you're already having.
You can also check the Technical Details (Gear icon) to see the activate connections.
If you're seeing a bunch of idled threads, try decreasing the number of threads.
Thanks, but I have been tinkering with the I/O Performance setting for a long time. No matter what I try it only does 1 read thread at a time.
I usually monitor my upload/download in the Technical Details, very helpful to get an understanding of the underlying processes.
When I upload it looks like it should (constantly writing according to my I/O Performance setting and then reading each chunk for verification).
But when I download it only ever shows 1 read thread, even though my setting currently is at 6 download threads.
Could it be some setting in Advanced Settings I need to change?
-
Is there a way to easily move content from my first drive to a new drive with increased chunk and partial read sizes?
I get good upload speeds (about 30-40MB/s), but I'm having trouble downloading data from the drive (only about 2-3MB/s), sometimes it slows down to less than 0.5MB/s.
Build number: 1.0.0.757
I also have very poor download speeds. ~3 mbps, on a 250 mbps line which I normally have no issues maxing out.
It seems it is only doing 1 download thread at a time, even though my limit currently is set to 10.
Can you change this behaviour? My understanding what that it could do multiple threads simultaneously.
-
Just thought I would check in to say that I have been running 4 upload/4 download threads at capped upload speed for me (50 mbit/s) without issues for a long time now.
Seems like it's working well again! Version 749.
-
Yes, I've been seeing this as soon as I increase the download and upload threads.
But it has been occuring even when I have something like 3-4 threads (upload and download combined).
Currently is seems stable enough at the latest 749 build.
No errors in the last 8 hours, but I was also taking it very slow:
1 download thread, 1 upload thread (throttled at 10 mbps).
Prefetcher disabled.
Currently trying 2 upload threads throttled at 20 mbps, hopefully it will remain stable.
I have only been using the service for little over a week (using the latest link from the main download page, 463?), but in the beginning when I was uploading close to 1 TB I didn't run into any problems at all as I recall. Maybe the occasional "rate limit exceeded" but it all went pretty smoothly.
I ran much more threads back then too.
-
Another idea that I had could be to allow for upload (and download) throttling per thread.
Currently the throttling in newer builds work for the total upload speed.
I.e if you set upload throttling to 20 mbps and have 4 threads open, then they are going to share the bandwidth.
My problem is that my uploads threads start and finish too quickly since I have 50 mbps upload (2 upload threads) - this leads to too many API calls and uploads stopping completely.
I was thinking if you could set for instance each thread can only use 1 mbps, then you can open several more threads going up at a slow pace.
That might lead to fewer API calls.
20 threads going at 1 mbps or lower with large chunks instead of 2 threads instantly completing and restarting at 50 mbps might be less stressful on the API.
Could be worth exploring maybe.
-
Would it be possible to allow the use of your own Drive API client ids in CloudDrive? If users were able to use their own ids then there would be no need to request a rate increase.
That sounds like a great idea if it's possible!
- Ginoliggime, KiaraEvirm and Antoineki
- 3
-
What is the latest recommended build and settings for best performance of Google Drive?
Tried 748, 730 and 725 yesterday but they all kept unmounting my drive.
Rolled back to 463 before going to bed and it has been going all night (although a bit slow).
Can you avoid the autodisounting if I change:
"Set "CloudFsDisk_MaximumConsecutiveIoFailures" to "0" and reboot to disable."
?
Is there any risk of corrupting the data doing that?
Also, do you plan to add larger chunks in the future - and if so, will you be able to change the structure of your drive or do you need to start over?
-
I have been getting "parameter is incorrect" all day as well.
Tried 725, 730 and 748.
Didn't encounter this error and unmounting of disk before, when I was running the latest stable build.
- KiaraEvirm, Antoineki and Ginoliggime
- 3
-
Hello,
Just upgraded to newest build (1.0.0.748) to see if I would get better Google Drive performance.
During install my Kaspersky antivirus detected Malvare.
"Detected: HEUR:Trojan.Win32.Generic
Location: C:\Progr....CloudDrive\CloudDrive.Service.exe"
Is this a knows issue? Should I ignore it?
CloudDrive Nearly Unusable Recently (Google Drive)
in Providers
Posted
I see.. But that means that the speeds I am seeing now, roughly 3-4 mbps, is what I should expect in download speed?
That's gonna take a long time to get the data back from the cloud then, seeing as I have more than 2 tb backed up already.