Throttle handling

Cloud Drive Mapper (CDM) manages provider throttling prevention in the following ways:

Retry dispersion

Retry dispersion is a method CDM uses to prevent multiple clients from retrying requests simultaneously after being throttled. By adding a random delay of up to 50% of the Retry-After interval, CDM staggers retries, reducing server load and improving recovery times. Learn more

Request concurrency and burst management

To prevent providers from being overwhelmed with bursts of requests, IAM Cloud limits CDM to six concurrent requests at a time. If this limit is reached, a 50ms delay is applied between each request to slow down the request rate. This throttling mitigation is consistently applied across all endpoint types in CDM. Learn more

User dispersion

User dispersion ensures that CDM avoids overwhelming the provider with simultaneous requests by distributing them more evenly across users and endpoints. Without dispersion, large organizations with thousands of users logging in around the same time would generate excessive concurrent requests, leading to throttling. CDM mitigates this by randomizing cache refresh intervals and startup processes, preventing synchronized spikes in requests. Learn more

Caching

CDM reduces provider requests and minimizes throttling through delta caching and request caching. Delta caching stores responses for dynamic drives, preventing unnecessary repeated calls. Request caching saves completed requests in memory, allowing CDM to resume from the last successful call after throttling instead of restarting the entire process. Learn more