Rate Limitations


Rate Limitations

Because cloud applications are accessed by potentially millions of connections, cloud providers must protect their platform integrity from the actions of an individual user or sets of users. As part of that protection most have implemented a form of rate limitation to control and throttle access.

Each individual client computer, account, or application has each request to the system recorded and counted at the platform side. If an individual client is exceeding a defined threshold (the value varies by platform) the platform will send an HTTP error code per the platform API instructions to slow down and wait before sending additional API requests.


SkySync, as any responsible client should, respects these rate limitations in order to prevent the platform from denying access.  You may first notice this type of warning message on your job history screen.  As indicated this may affect your throughput, transfer, or overall migration speeds.


Here are some possible suggestions you can pursue with your storage provider.

Some cloud vendors will reduce rate limitations temporarily for clients upon request while others throttle by API Key or other scaling mechanism. It doesn’t hurt to ask if you have those options available to you.

If the rate limits are account based, having multiple admin accounts and manually structuring jobs and connections to split overall processing is sometimes possible with some planning.

You can reduce the amount you see the messages by reducing the SkySync Parallel Writes setting, slowing down the transfers to put less pressure on the rate limits.

Regardless of the behavior of the specific connectors being used, SkySync will maximize the performance within its current settings and the resulting rate limit messages can be ignored if there is no avenue for improvement.


Please contact Portal Architects support for assistance with this article.


Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk