Throughput

Are EdgeKV operations performed from an EdgeWorkers function throttled?

Throttling is enforced when requests need to go to the persistent store. As such, all write and delete requests are subject to the throughput limits listed in the EdgeKV product limits.

For read requests, the throughput limit is only enforced:

• On requests for items that do not have a local copy on the edge server executing the EdgeWorkers function making the request.
• Or when the requested items were invalided due to a recent write or delete.

How does the read/write ratio impact my throughput limit?

When you update an item by performing a write or delete operation, subsequent read requests for that item have to go to the persistent store. There is also an increased chance that subsequent read requests of other items have to go to the persistent store. When a request goes to the persistent store the throughput limit is applied.

Minimizing the update frequency will reduce the chances of hitting the throughput limit.

How can I drive more traffic while staying within the EdgeKV throughput limits?

To reduce the chance of hitting the throughput limit:

• Maintain a read/write ratio of 98/2 read/write or better.
• Avoid long tail data requests (data that is infrequently accessed).

Are the EdgeKV request limits enforced globally?

Yes, the limits are enforced globally.