Jump to content
Covecube Inc.
  • 0

CloudDrive + GoogleDrive


Question

Ive been reading various posts about this setup and I am actually very curious what are other users setup to achieve their full connection as ive tried different settings that are posted around here and it just does not seem to get to some of the screenshots ive seen. [This being on a 600/900 connection]

Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

large chunk and lots of threads does the trick. used to get better upload speeds with 100 mb chunks. they were removed though, but hoping for them to return soon :-)

 

Hmm so since 100mb chunks are gone, is there a specific setup that you prefer ? I am currently on .463 with the following:

  • 20MB Chunks
  • Download Threads: 8
  • Upload Threads: 10
  • 60MB Trigger
  • 80MB Forward
  • 120 Seconds

With the above setup my speeds are not that bad, but I constantly become throttled. Was hoping someone would have a sort of "golden" setup.

Link to post
Share on other sites
  • 0

you are using an old version!

 

http://dl.covecube.com/CloudDriveWindows/beta/download/?C=M;O=D

 

follow this url for the newest updates! newest is .597 LOTS of speed improvements since then!

 

you can increase the minimum download size while creating/attaching to get it to download larger pieces and get throttled a lot less! i still get throttled a lot but 100 mb chunks will improve that!

 

Remember to make a new drive with the new version since stuff changed

 

You can find their changelog here:

 

http://dl.covecube.com/CloudDriveWindows/beta/download/changes.txt

Link to post
Share on other sites
  • 0
  • 60MB Trigger
  • 80MB Forward
  • 120 Seconds

 

Try reducing the prefetching trigger (this is how much needs to be read before it's triggered). 

Try setting it to 20MB ( or lower) 

 

The Forward is how much it reads, and the timeout is how long it's retained.  These are a bit trickier, and are what need playing with. 

(See below)

 

 

Welcome to the bleeding edge. :)

 

I'd recommend 1.0.0.592, as it's the latest numbered build in the changelog. 

 

Specifically, the numbered builds are the "final" release for a fix/improvement.  Anything above that is "in flux" and much more likely to cause issues. 

 

In fact, we'd recommend the second numbered build, for stability. 

 

 


 

 

 

Specifically, if you have a very high speed connection (eg 200+ mbps for both upload and download), there are a number of things to help optimize the drive. 

 

Block Sizes

  • Storage Chunk Size
  • Minimum Download Size

This controls the actual size of the raw data blocks that we use.  Increasing the storage chunk size increases the actual size on the provider, while the "minimum download size" changes the discrete "partial read" unit size that we use. 

 

In either case, a higher value may improve performance as it may allow the connection to "get up to speed", as well as reduce HTTP overhead for the connection. 

 

However, these are set during the creation of the drive and cannot be changed once the drive is created. Meaning that you'd need to create a new disk if you want to change this. 

 

Additionally, the larger the chunk size, the longer it may take to download (especially on slower connections), and increases the disk latency. Latency can cause performance issues on the drive, such as wait times while accessing data, enumerating directories, etc. 

 

Threading

  • Upload threads
  • Download threads

Pretty much what it sounds like. Each thread is capable of uploading or downloading a chunk (partial or full) at a time. More threads means that you can have more active connections at the same time.  This can greatly increase the speed of access, especially if prefetching is configured "properly". 

 

 

Basically, this controls the level of parallelization. But this only helps up to a point. If you have 20 threads enabled but only need 4-5... they're wasted. 

 

This can be changed at any time. 

 

 

Prefetching: 

 

  • Trigger
  • Forward
  • Timeout
The Trigger is how much data needs to be read for prefetching to occur.  Smaller means more aggressive, while larger means that you rely on your connection more and are more likely to experience latency. 
 
The Forward is how much data is grabbed.  Eg, how far to read ahead.  You may want to set this in increments of the "minimum download size" (or the storage chunk size, if not available).  That way, this is more optimized based on your drive config.  
 
 
Timeout is how long the data *must* be retained before it can be let go. This depends on a lot of factors, but especially the forward. The higher the Forward value is, the higher the timeout needs to be (to ensure proper functionality).   However, too long can adversely affect the adaptive/learning functionality of the cache. 
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...