3 ms·

Yep: 50ms CPU time is a lot. Network calls aren’t meaningful CPU time, which is why you can use Workers to call to third party APIs. You may want to be mindful

Yep: 50ms CPU time is a lot. Network calls aren’t meaningful CPU time, which is why you can use Workers to call to third party APIs. You may want to be mindful of doing that during a user request as it now adds a dependency & latency, but it’s certainly possible to call out to a translation API or mapping API & cache the results...

davidjnelson 8y ago
> Network calls aren’t meaningful CPU time I understand how async io works. I'm used to AWS Lambda charging for request start to end time regardless of cpu usage.