JHi! I'm currently working with functions & pages for the first time, and I have a question regarding their cap for CPU time.
We have a function that has a median CPU time of 200ms (althought with very low req/s number). But the docs for the free plan, which we can hopefully stay on, says up to 10ms CPU time per request.
My question is, how does that work? We're already breaking that cap by 20x. Is it accumulative per month or something? Or are we going to be forced somehow cut that down to 50ms, which is the starting tier for paid plans?
We have a function that has a median CPU time of 200ms (althought with very low req/s number). But the docs for the free plan, which we can hopefully stay on, says up to 10ms CPU time per request.
My question is, how does that work? We're already breaking that cap by 20x. Is it accumulative per month or something? Or are we going to be forced somehow cut that down to 50ms, which is the starting tier for paid plans?
EWhile I couldn't tell you 100%, I'm pretty sure it's taken as an average and allows for some amount of bursting, I don't believe you would be able to achieve 200ms CPU time consistently, most likely it's more lenient because the request rate is lower.
This isn't guaranteed though, and I wouldn't be surprised if requests started failing at any moment for exceeding resource limits.
Your best bet to guarantee you can keep doing 200ms of CPU going forward is to upgrade to Workers Paid for $5/mo and then change to the Unbound usage model which allows for up to 30 seconds of CPU time per request, with billing for the time the Worker takes to execute. There is a very generous amount of included usage in that $5
This isn't guaranteed though, and I wouldn't be surprised if requests started failing at any moment for exceeding resource limits.
Your best bet to guarantee you can keep doing 200ms of CPU going forward is to upgrade to Workers Paid for $5/mo and then change to the Unbound usage model which allows for up to 30 seconds of CPU time per request, with billing for the time the Worker takes to execute. There is a very generous amount of included usage in that $5
JWow, that response time! 
Okay, duly noted. I will continue experimenting with it and see were it lands. Maybe we'll end up with the $5 plan, that seems pretty sweet.
Thank you so much! @Erisa | Out of office
Okay, duly noted. I will continue experimenting with it and see were it lands. Maybe we'll end up with the $5 plan, that seems pretty sweet.
Thank you so much! @Erisa | Out of office
