3 ms·
Kenton describes a bit here what they measure and how: https://community.cloudflare.com/t/how-is-cpu-time-per-request-measured-in-cloudflare-workers/49964/3 ht
by NicoJuicy 3y ago
Kenton describes a bit here what they measure and how:
https://community.cloudflare.com/t/how-is-cpu-time-per-request-measured-in-cloudflare-workers/49964/3 https://community.cloudflare.com/t/how-is-cpu-time-per-reque...
Cloudflare is only billing that actual cpu-time.
Edit: this is a better resource https://blog.cloudflare.com/workers-pricing-scale-to-zero/ https://blog.cloudflare.com/workers-pricing-scale-to-zero/
- NicoJuicy 3y agoThat's partially why so many llm/ai apps use cloudflare. An API call can take a lot of seconds. While Cloudflare only bills cpu-time ( eg. 10 ms. ). Other providers bill those seconds too as "duration", while the CPU was just sitting idle.
- lozenge 3y agoI can see both sides because you are reserving that amount of RAM while your process is running. The Lambda price is also proportional to the RAM reserved.
- NicoJuicy 3y agoWell. I thought that this was possible because Cloudflare eliminated cold start delays. So there's no RAM reserved either, I guess. ( can someone correct me if I'm wrong?)