Freppa

I think I'm coming closer to the issue: It seems that there is a delay with G-drive for when it starts. If I start a copy, it takes 10 seconds before it starts executing upon it. If I start a Plex-task, it takes 15 seconds before anything is happening on G-drive If I run a movie via VLC, it's down to 10 seconds before anything happens. I have tried towards my Amazon and there is like 1-2 seconds delay according to the schedule above.

No go. Still slow. Will try some alternative routes in order to check for faults. I'll get back. Any other suggestions in the meantime is welcome. /F

Hi, After trying with ACD I got sick of all the throttling and decided to get a GDrive account. I have a 1gb/1gb line and have now have all data on Gdrive, however now Plex takes forever to start. With ACD it took around 12 seconds to start a movie and scrolling would take as long (prefetch 600mb) and I would max around 80Mbps. With GDrive it takes around 45 seconds to start a movie, but it basically is downloading the whole movie (prefetch 600mb) and I max around 350mbps. I haven't changed anything on Plex and the only difference I can see between ACD and Gdrive (apart from the lack of throttling - thank God) is that I had ACD set at 50mb chunks, with Gdrive I can only set 20mb chunks (storage). Any thoughts? I am also concerned that I cannot max the line or at least come close. I have real time download speeds at around 800mbps but with Stablebit and Gdrive i cannot get it over 350 ul/dl. /F Stats: Threads 10/10, Prefetch trigger 1mb, prefetch forward 600mb

...but performance is extremly poor. dl @ 1mbit/s

it just came back up. wohooo!

Hi, Was there any resolution on this one? Since AWS is having issues right now I logged in to my web dashboard and it seems that approx 400mb of files are now identified as pictures. How can I identify what "real" file those 400 are pertaining? /F

Ah, time to visit their blog to check if they have an issue. Thanks Weirdomusic!

Hi friends, Today I had my Fiber upgraded (changed vendor) to 1000/1000 which meant that I lost connection to my drives. I only get the dreaded HTTP Status 429. Now, I have probably missed what I can do to not incur the wrath of the throttling Gods over at Amazon, but could I get some guidance (I am just about to migrate from amazon to Google Drive since Amazon doesn't seem to end up on the positive list - go figure on the timing.....) This is what the logs tell me. 0:22:06.0: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 1,000ms and retrying. 0:22:07.2: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 2,000ms and retrying. 0:22:09.3: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 3,000ms and retrying. 0:22:12.4: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 4,000ms and retrying. 0:22:16.5: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 5,000ms and retrying. 0:22:21.7: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 6,000ms and retrying. 0:22:27.8: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 7,000ms and retrying. 0:22:35.0: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 8,000ms and retrying. 0:22:43.2: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 9,000ms and retrying. 0:22:52.3: Warning: 0 : [ValidateLogins] Error instantiating management provider. HTTP Status 429 Tips/tricks? /F PS: Perhaps should add that I have upgraded to .858 a couple of days ago if that makes any difference.

To my understanding, pre-release has nothing to do with functionality or performance. It is only the developers seting this banner to show that this is pre-release (Stablebit, not Google) and that a release candidate/version is pending. /F

If you are running a late version (.83x, it seems to work flawless, however before that it was a bit of a gamble. Try making the cache small so you only have to upload a small amount and try.

Interesting. It would be interesting to understand how ACD thought when developing such a solution. I must say, if Google Drive Unlimited wasn't so expensive to procure, I would probably switch at this point.

Drashna, I have uploaded the two files to dropbox for your viewing pleasure

Still the same issue. Small file, 15mb, maxed 100mbit line, took 4 times as long.

Ok, I'll correct myself: Upload verification is ​not​ on. I'll run some tests on uploading with newest release to see if it continues over 100%. I'll get back to you on that one.

Check! Thank you.

Upload verification is on, yes. However isn't that normally handled on checksum? Keep up the great work! (And let us know if we can help on putting pressure on Amazon Cloud Services 😀)

Update: after three attempts it came back up. Everything seems normal. Drashna: what is "authorative mode"?

I updated to version .834 this morning. Now I cannot get the drive (Amazon Cloud) to mount at all. After a while I get "HTTP 429 error". Any thoughts? edit: For clarification: It was working flawless prior to upgrade. ​The service logs shows a lot of activity, including throttling. A snip: 4:24:03.4: Information: 0 : [ChunkIdSQLiteStorage:23] chunks IDs: 47539,47544,47546,47549,47564,47570,47571,47587,47588,47595,47598,47602,47612,47630,48534,48545,48553,48561,48569,48574,48575,48597,48603,48605,48622,48623,48631,48634,48636,48640,48647,48649,48653,48674,48678,48680,48685,48691,48694,48695,48698,48705,48711,48716,48726,48728,48731,48732,48750,48759,48780,48782,48783,48784,48805,48808,48817,48831,48840,48848,48854,48855,48887,48892,48906,48913,48926,48931,48947,48956,48987,49007,49008,49010,49020,49023,49027,49030,49040,49065,49068,49083,49089,49094,49098,49112,49115,49118,49123,49127,49128,49144,49147,49155,49160,49179,49181,49202,49215,49219 4:24:03.6: Information: 0 : [ChunkIdSQLiteStorage:23] chunks IDs: 47620,47627,47631,47643,47645,47646,47665,47682,47708,47710,47711,47742,47757,47762,47780,47787,47788,47798,47805,47821,47829,47851,47872,47877,47892,47896,47901,47905,47927,47930,47937,47943,47956,47959,47987,48020,48023,48045,48063,48071,48083,48086,48096,48106,48107,48126,48129,48167,48176,48185,48189,48190,48198,48201,48203,48216,48219,48220,48229,48240,48259,48260,48263,48274,48288,48301,48308,48313,48316,48326,48331,48337,48341,48351,48370,48372,48377,48415,48416,48419,48423,48429,48436,48466,48472,48474,48483,48486,48487,48501,48502,48518,48528,48539,48541,48550,48562,48563,48576,48579 4:24:03.7: Information: 0 : [ChunkIdSQLiteStorage:23] chunks IDs: 48586,48589,48598,48602,48608,48633,48644,48648,48679,48684,48687,48693,48696,48700,48703,48714,48721,48723,48725,48727,48729,48738,48740,48751,48764,48773,48776,48778,48794,48795,48797,48807,48811,48823,48829,48914,48941,48944,48945,48955,48969,49006,49009,49013,49014,49019,49048,49049,49051,49059,49079,49080,49084,49086,49091,49095,49101,49102,49105,49109,49133,49150,49165,49177,49178,49187,49198,49205,49206,49210,49212,49213,49221,49244,49246,49257,49263,49272,49278,49280,49283,49313,49314,49315,49327,49333,49334,49337,49339,49349,49350,49355,49358,49363,49368,49384,49398,49408,49409,49422 4:24:04.1: Warning: 0 : [ApiAmazonCloudDrive] Server is throttling us, waiting 1,000ms and retrying.

This is a topic I think have been discussed before but is still an issue on my setup. If I upload 1GB of data, it takes three to five times as long time as if I was uploading directly utilizing the same speed. I looked at the "technical details" and noticed something peculiar - progress on some threads where over 100% in completion. Why would that be?

I am sure that I could use some third-party solution for this, but just as a suggestion: Could you please allow for an email/SMS to be sent when service throws exceptions/warnings? It would be great to know the status of the disk when using headless systems to which I do not log on every day.

Ah, just realized one more thing: When setting up the disk, I increased chunks to 50MB. Standard was 1MB. That meant a lot of I/O just to fetch the data, hence not able to stream with desired result.

I use Amazon (trial vendor) but it works great. I have 250/100 mbit and I have set prefetch at 400, keep 600, 10/10 threads. I use PLEX as my server setup.

Just to confirm: With version .793 I have not been able to reproduce the error where the system goes into recovery after reboot. I have also tested with having plex running and getting the same result. One thing I haven't been able to test if when Windows 10 automatically reboots after an update has been performed and if that has any impact, but I'll hold of on that for now.

In my case no - it is stored on a local SSD which resides on the same disk as the OS. Before reading this, I upgraded to .793 and I haven't been able to replicate it yet, however I had one thing setup differently than when it happened before (which I can test tonight): I haven't had PLEX running on the server when I now have tested this feature. Don't know if that is part of the problem but since PLEX is the only data stored on my ACD, it could affect.

I am very sad to hear that - all though I understand that parts of their business models are based on matching files and avoiding double-storage, I.e. limiting storage cost, it would mean that I, and probably many with me, need to rethink the strategy vs. Amazon. I like your product since it fits my purposes so I will continue using it, but I think you would do us all favor to take the discussion on above note with Amazon now to either put a period to the discussion (I.e. they will be removed as supplier) or to get them to accept the setup. This in turn would push my own decision going forward which I rather do now than later. BR Fredrik