3 ms·

That's not the only thing that has excess fees in AWS/Azure/ .... Eg. For cloudflare workers. If you're worker is making an outgoing request ( db / rest) it's

That's not the only thing that has excess fees in AWS/Azure/ .... Eg. For cloudflare workers. If you're worker is making an outgoing request ( db / rest) it's not considered cpu-time and it's not counted towards that either ( in cloudflare ofc). While this is a hidden profit of many cloud providers :)

andrewstuart 3y ago
Can you explain more? Wait time isn’t calculated as compute?
- 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 ago
    That'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 ago
      I 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 ago
        Well. 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?)