4 ms·
Ah yeah makes sense. Really interesting that cf workers limit you to 50ms cpu time rather than wallclock time, makes lots of send-then-wait scenarios possible/w
by nhoughto 6y ago
Ah yeah makes sense. Really interesting that cf workers limit you to 50ms cpu time rather than wallclock time, makes lots of send-then-wait scenarios possible/way cheaper.
- qwtel 6y agoactually there appears to be a limit to this. i’ve never been able to perform more than ~50 http requests per invocation, leading me to believe that they are “billed” with 1ms cpu time.
- nhoughto 6y agoYeah it’s not _just_ 50ms cpu, there are other constraints like 50 sub requests, 6 open connections etc. Still faaairly generous, good luck getting 50 sub requests done in 50ms if you had to measure against wallclock =)