How to use the result
- Enter the measured p95 or p99 execution duration for the complete unit of work, not an optimistic local average.
- Add margin for cold starts, network variance, cleanup, retries, and the time needed to persist a resumable checkpoint.
- For each apparent fit, verify the eligible plan, runtime, invocation mode, gateway timeout, client deadline, and configured function timeout.
How to interpret the answer
The comparison checks documented execution ceilings only. A platform marked as fitting can still fail when an API gateway, browser, SDK, reverse proxy, database call, queue visibility timeout, or deployment-specific setting ends the request earlier. Long work should remain idempotent and resumable even when the nominal ceiling is generous.
A passing result means the entered workload fits the documented constraint represented by this tool. It does not guarantee latency, availability, cost, throughput, or acceptance by every upstream and downstream service.