Performance considerations

Get familiar with these best practices to reduce the risk of traffic overload or other performance incidents.

  • You may create a spike in the load on your origin if you send too many concurrent requests to remove or invalidate objects. To reduce the risk of load spikes, instead of specifying all objects in one submission, space the refresh requests over time. You can also combine multiple objects into fewer purge requests.

  • Delete-based requests may cause more load than conditional invalidation-based ones. Use invalidation unless all objects have changed.

  • The total size of the objects in the request can't exceed 50,000 bytes.