Jump to content
Covecube Inc.

KiLLeRRaT

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    2

Reputation Activity

  1. Like
    KiLLeRRaT reacted to ezek1el3000 in Google Drive: The limit for this folder's number of children (files and folders) has been exceeded   
    My advice; contact support and send them Troubleshooter data. Christopher is very keen in resolving problems around the "new" google way of handling folders and files.
  2. Like
    KiLLeRRaT reacted to Chase in Google Drive: The limit for this folder's number of children (files and folders) has been exceeded   
    Unintentional Guinea Pig Diaries.
    Day 5 - Entry 2
    *The Sound of Crickets*
    So I'm in the same spot as I last posted. My second drive is still at "Queued to perform Recovery". If I knew how to force a reauth right now I would so I could get it on my API. Or at the very least get it out of "queued"
    Perhaps our leaders will come back to see us soon. Maybe this is a test of our ability to suffer more during COVID. We will soon find out.
    End Diary entry.
  3. Like
    KiLLeRRaT reacted to srcrist in Google Drive: The limit for this folder's number of children (files and folders) has been exceeded   
    Hey guys,
    So, to follow up after a day or two: the only person who says that they have completed the migration is saying that their drive is now non-functional. Is this accurate? Has nobody completed the process with a functional drive--to be clear? I can't really tell if anyone trying to help Chase has actually completed a successful migration, or if everyone is just offering feedback based on hypothetical situations.
    I don't even want to think about starting this unless a few people can confirm that they have completed the process successfully.
  4. Like
    KiLLeRRaT got a reaction from Antoineki in Google Drive Rate Limits and Threading/Exp Backoff   
    Hey Guys,
     
    I got slow transfers with Google Drive, and set the threads to 12 up and 12 down.  This worked for a while and everything was a bit faster.
     
    For the last two days, I have been getting countless Rate Limit Exceeded exceptions, even running 1 up and 1 down thread.
     
    I check out online in the Google Drive API guides and found a bit about exponential backoff.
     
    So a few questions/thoughts:
     
    Is exponential backoff implemented for the Google Drive provider? If I set the provider to use say 12 up and 12 down threads, do they all get blasted out using multiple requests at the same time? (causing rate limit exceptions later on)? Would it work to have something like a 'request gatekeeper' where you can set your own rate limits client side so that no matter how many threads you run, it always obeys that limit you set, and so that there is a 'master exponential backoff' in place? Is there at all a possibility to look at the provider implementation code? Or is this fully baked into the product? It'd be good if there was an API to allow anyone to build their own providers.
     
    Thanks for a good product!
     
     
    EDIT: Also, how will all the rate limiting work if you added say 5 Google Drives, each with 12 threads up and down? Quite quickly you will be making a TON of requests...
  5. Like
    KiLLeRRaT got a reaction from Ginoliggime in Feature Request - Dynamic prefetch size   
    Hey guys,
     
    Good to see that the releases are getting more and more solid.
     
    I just had a thought while looking at my transfers/prefetching.
     
    What if you had the prefetch forward value automatically scale based on the hit rate of the prefetch? Perhaps you can provide a range, e.g. between 1 MB and 500 MB based on hit rate. 
     
    For streaming movies, a large prefetch works well (e.g. 150 MB, or even more). The hit rate will be good, thus growing the prefetch size more and more.
     
    If I later then start looking through photos that are only 3 MB each, the hit rate will get pretty terrible, and thus scale back the prefetch again to say 1 MB again.
     
    Just thought this could improve the general bandwidth use, and ultimately performance.
     
     
  6. Like
    KiLLeRRaT got a reaction from Ginoliggime in Google Drive Rate Limits and Threading/Exp Backoff   
    Hey Guys,
     
    I got slow transfers with Google Drive, and set the threads to 12 up and 12 down.  This worked for a while and everything was a bit faster.
     
    For the last two days, I have been getting countless Rate Limit Exceeded exceptions, even running 1 up and 1 down thread.
     
    I check out online in the Google Drive API guides and found a bit about exponential backoff.
     
    So a few questions/thoughts:
     
    Is exponential backoff implemented for the Google Drive provider? If I set the provider to use say 12 up and 12 down threads, do they all get blasted out using multiple requests at the same time? (causing rate limit exceptions later on)? Would it work to have something like a 'request gatekeeper' where you can set your own rate limits client side so that no matter how many threads you run, it always obeys that limit you set, and so that there is a 'master exponential backoff' in place? Is there at all a possibility to look at the provider implementation code? Or is this fully baked into the product? It'd be good if there was an API to allow anyone to build their own providers.
     
    Thanks for a good product!
     
     
    EDIT: Also, how will all the rate limiting work if you added say 5 Google Drives, each with 12 threads up and down? Quite quickly you will be making a TON of requests...
  7. Like
    KiLLeRRaT got a reaction from KiaraEvirm in Google Drive Rate Limits and Threading/Exp Backoff   
    Hey Guys,
     
    I got slow transfers with Google Drive, and set the threads to 12 up and 12 down.  This worked for a while and everything was a bit faster.
     
    For the last two days, I have been getting countless Rate Limit Exceeded exceptions, even running 1 up and 1 down thread.
     
    I check out online in the Google Drive API guides and found a bit about exponential backoff.
     
    So a few questions/thoughts:
     
    Is exponential backoff implemented for the Google Drive provider? If I set the provider to use say 12 up and 12 down threads, do they all get blasted out using multiple requests at the same time? (causing rate limit exceptions later on)? Would it work to have something like a 'request gatekeeper' where you can set your own rate limits client side so that no matter how many threads you run, it always obeys that limit you set, and so that there is a 'master exponential backoff' in place? Is there at all a possibility to look at the provider implementation code? Or is this fully baked into the product? It'd be good if there was an API to allow anyone to build their own providers.
     
    Thanks for a good product!
     
     
    EDIT: Also, how will all the rate limiting work if you added say 5 Google Drives, each with 12 threads up and down? Quite quickly you will be making a TON of requests...
  8. Like
    KiLLeRRaT got a reaction from Ginoliggime in Beta Version Discussions   
    Hey,
     
    Would it be useful to have a sticky on here, where it's posted when a new beta version comes out, along with what people run into and find in that version? Basically a copy of the changes.txt, but people can then post comments on it etc...
     
    e.g. The issue we had where drives become corrupt... That way it's quick to realize that you probably shouldn't update to the update until it's resolved...?
     
    Just a thought!
     
  9. Like
    KiLLeRRaT got a reaction from Christopher (Drashna) in Files starting to go corrupt, Cloud Drive throws no errors   
    Hey Chris,
     
    Yeah I haven't lost anything important, I have quite a number of backups of my important stuff on multiple services and also multiple physical drives on separate locations.
     
    I  was just hopeful with this since I just sorted out my TV Show library and took a while to get sorted out and working the way I wanted, so was hoping I wouldn't have to do it over again heh.
     
    Thanks for the help and so on though, loving the product so far!
×
×
  • Create New...