Jump to content
Covecube Inc.

Search the Community

Showing results for tags 'googledrive'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
    • Nuts & Bolts
  • BitFlock
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. i have fiber and i wanna get more storage via google drive and my main issue is the uploud speed is there a way for me to push the upload/download threads past 20 ?
  2. I'm trying out CloudDrive with Google Drive, and have created a small drive for testing. If I go this route, I'll have a lot of stuff there, including some things I'd like to have served by Plex. I'd like to test the performance when the content has to be pulled from the cloud. I haven't put enough into the cloud drive to over flow the cache yet. Will it just sit in the cache forever, or do things ever stale out? Or failing that, can I flush the cache, so I can force CloudDrive to have to pull from GDrive to fulfill a request? Thanks!
  3. Is this where I should be submitting feature requests? I ask because I have just gone through the forums about the Google Drive API limits/throttling having bumped up against the infamous userRateLimitExceeded issues - presumably after hitting their 750GB per day limit. What I noticed was that once this rate limit is hit there isn't really anything for the application "to do" except for cache writes until Google lifts the ban/quota resets/etc. but I noticed that the write attempts just keeps hammering google which takes bandwidth unnecessarily. I was curious about the potential to just stop making the attempts after a while, and just go dormant (though continuing to write data to cache) until the throttle is lifted? I would imagine the logic would be something like: CloudDrive starts receiving userRateLimitExceeded responses and it then puts itself in a local caching only mode (opt-in or by default - doesn't really matter to me) CloudDrive then starts sending some type of a "canary" small data packet every few minutes to test and see if Google Drive API and/or Google Drive Backend are accepting writes again, and then start writing full chunks again whenever applicable. Rinse/repeat. I realize that there is a method people have used to throttle the traffic in the settings basically to make it impossible to hit the 750GB per day quota but, in my tests for what I am using CloudDrive for I expect to ONLY stumble upon this limit maybe 10% of the time. The other 90% of the time I want to be able to use the full on bandwidth. So while a mbps throttle can help 10% of the time it ends up being an unnecessary bottleneck for the other 90%. Does this sound useful to people or am I crazy? I don't mind hitting the limit from Google every once in a while but I don't really understand why the CloudDrive cannot be more efficient when it becomes clear that the upload quota has been reached. To me it looks like it keeps trying to write the same chunks over and over (sending the full chunks all the way to Google, for the chunks to end up being denied at the door) I think for bandwidth efficiency something like this could be helpful. But maybe this is just me trying to min/max the efficiency of the application too much in a rare situation. Thanks
  4. Reading through these steps I originally missed the tidbit at the end: So, to be clear, does this mean I am unable to switch an existing drive to use my newly setup API keys. I went through this process 3 or 4 days ago and I just signed back into the Google Cloud Console and looking at the API monitoring sections it shows no usage, which is what triggered me to go reread the document. I am looking to confirm if the changes made in the ProviderSettings.json will not kick in until I make a NEW DRIVE connection and what that means for a drive that was mounted/connected BEFORE going through this process. Basically is there a way to use my keys with a drive that was original setup using the applications embedded pool of API keys or will I have to create a new drive and transfer everything from one to the other? Forgive me if this seems like a stupid question, I know enough to be dangerous so I cannot imagine why I would have to go through a transfer process but that could just be my ignorance showing. Thanks in advance all!
  5. I am testing Stablebit to upload to my GSuite Account. I setup a 10 TB Encrypted Drive and are currently uploading Large Files to it. It has been uploading for a day or so and the speeds seem to be steady from the 1 GB expandable cache of 40 to 45 mbps, about 18-19 GB per house I have 1 GB download, 1 GB Upload Fiber line. Is this the normal upload to google or should I be getting more. Attached a pic If more, anyone have any hints on increasing this. Thanks in advance!
  6. Hi, I've noticed frequent drive unmounts recently. The log looks like this - the drive still works, but very poorly, then eventually it just drops the drive entirely. It seems like some google side rate limiting, but I'm interested if anyone else is seeing this, or has any ideas of a way to work around it? Cheers 18:03:34.6: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:220] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:03:34.6: Warning: 0 : [ApiHttp:209] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:209] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:205] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:212] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:219] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:02.4: Warning: 0 : [ApiHttp:206] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:22.7: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:23.5: Warning: 0 : [ApiHttp:216] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:05:24.3: Warning: 0 : [ApiHttp:42] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:218] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:208] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:58.9: Warning: 0 : [ApiHttp:216] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:59.0: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:06:59.4: Warning: 0 : [ApiHttp:49] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:219] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:203] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:166] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:213] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.2: Warning: 0 : [ApiHttp:220] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:07:27.6: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.2: Warning: 0 : [ApiHttp:205] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.3: Warning: 0 : [ApiHttp:215] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable). 18:08:02.3: Warning: 0 : [ApiHttp:208] Server is temporarily unavailable due to either high load or maintenance. HTTP protocol exception (Code=ServiceUnavailable).
  7. Hi there, I have been using StableBit CloudDrive for around a month on a dedicated server. The upload speed is always between 0 and 200 Mbit/s per drive with an average of 150 Mbit/s. Since build 1.0.0.753 BETA the download speed maxes out on 10 Mbit/s which results in stuttering videos with PLEX and extremely slow copying. The number of threads doesn't seem to matter, I tried 2, but I also tried 5, 10 and 20. I also tried another Google account, but that also doesn't help. I tried both a drive block size of 10 and 20MB, but it really seems to be a bug with the software, because changing settings doesn't help a bit, the download speed does not improve. - Calvin
×
×
  • Create New...