Context: 90% of errors reported by clients on the Stable release channel are throttled by the backend service and never logged. By default, GCP has a 10 GHz-seconds limit on total CPU allocation for Cloud Functions invocations. A recent surge in errors from a (fixed) high-frequency error pushed us over the edge, and we hit our daily quota for CPU allocation.
For now, I've requested a quota increase to better handle load spikes like this. To reduce some of that request load, we can move the 90% throttling of Stable traffic to the client. This can be a very simple check implemented by the runtime that would drastically reduce backend load.
/cc @jridgewell
Context: 90% of errors reported by clients on the Stable release channel are throttled by the backend service and never logged. By default, GCP has a 10 GHz-seconds limit on total CPU allocation for Cloud Functions invocations. A recent surge in errors from a (fixed) high-frequency error pushed us over the edge, and we hit our daily quota for CPU allocation.
For now, I've requested a quota increase to better handle load spikes like this. To reduce some of that request load, we can move the 90% throttling of Stable traffic to the client. This can be a very simple check implemented by the runtime that would drastically reduce backend load.
/cc @jridgewell