Is it worth refactoring our AWS Lambda monolith into Cloudflare Workers to save on invocation costs, or will the CPU time limits break our PDF generation pipeline?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Is it worth refactoring our AWS Lambda monolith into Cloudflare Workers to save on invocation costs, or will the CPU time limits break our PDF generation pipeline?
3 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 3 queries…
Searches and sources
ChatGPT3 real searches · gpt-6
Cloudflare Workers CPU time limits paid plan 2026 maximum duration memory limits official docs Google ↗
Cloudflare Workers pricing requests CPU time 2026 official pricing Google ↗
AWS Lambda pricing duration memory timeout ephemeral storage 2026 official docs Google ↗
- Limits · developers.cloudflare.com
- Request timeout · docs.aws.amazon.com
- Pricing · developers.cloudflare.com
Queries
3 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Cloudflare Workers CPU time limits paid plan 2026 maximum duration memory limits official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Cloudflare Workers pricing requests CPU time 2026 official pricing OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
AWS Lambda pricing duration memory timeout ephemeral storage 2026 official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |