For some use cases, Bundled makes sense, for others, Unbound makes sense. Again, flexible + affordable is what we're after as we mention in that blog post!
I wouldn't really compare the pricing because they're different use cases.
* Bundled workers can't do 100ms of compute per request. They're limited to a max of 50ms.
* Unbound scripts can use as much or as little compute as you want per request up to a maximum wall time of 30s.
* Cron triggers can use up to 15 minutes of wall time per invocation (but can't handle requests).
If you can do all I/O & CPU within 50ms, then unbundled might theoretically be cheaper still but that's just on my coarse napkin math. It's hard to correctly model how many Workers you'll end up needing during the month which provides large error bars (e.g if you get 100 requests per second across the globe, the cost will be very different than if you got 100 rps from just 1 machine for the month).
The option to pick is the one that satisfies the shape of the problem you are using. Predicting the price you'll end up paying is a bit hard to estimate correctly vs just seeing what your bill ends up being.
> Cloudflare will bill for duration charges based on the higher of your wall time or CPU time, with a multiple applied to the CPU time to account for the processing power allotted to your script.
Does anyone know how the CPU time is calculated? What's the "multiple"?
Are there any minimums in terms of execution time? I remember when Workers Unbound was announced I didn't see any mention of minimums anywhere, but other provides have them. For example, Azure [2]:
> The minimum execution time and memory for a single function execution is 100 ms and 128 mb respectively.
I remember thinking the examples in the original announcement assumed no minimums. Even if there's a 100ms minimum, are short lived executions that don't do any waiting on I/O cheaper as Unbound Workers now?
Assuming I calculated that right, it's $0.30 per million for 100ms of execution vs $0.50 per million for a normal Worker. There's wall time vs CPU time, but that's a pretty huge discount for short lived executions, right? Am I way off on something? It seems too good to be true. Lol.1. https://developers.cloudflare.com/workers/platform/pricing#w...
2. https://azure.microsoft.com/en-ca/pricing/details/functions/