Skip to main content
These limits cover typical use under normal operating conditions, and they keep one script from taking resources away from everyone else’s. Occasional spikes above a limit are tolerated. A script that consistently hits or exceeds one will be throttled or terminated.

Staying within the limits

  • Review your script’s code so it finishes within the time and memory limits.
  • Keep the number of subrequests down, and cache responses where you can.
  • Watch the logs and statistics for your script so you catch a growing problem before it turns into a limit violation.

CPU Time

CPU time is measured while the script is actually using the CPU to run your logic, and it directly affects how quickly a script can respond. It is allocated per request, so every execution gets the same share of processing time. Infrequent spikes in CPU usage are fine. Going over the limit again and again will lead to the script being terminated.
Last modified on August 17, 2026