Worker limit request
Ah I see the request, you sure you need that much CPU time and not just wall time? Wall time is unlimited
Are you hitting CPU time limits today?
12 Replies
Yeah I hit worker execution limit for my report functions. I can send you it's name if that helps
As wait time is unlimited according to the docs, I assume this is the thing timing my workers out
are you doing this in a cron trigger?
For context it's a worker consuming from a queue and then generating a report. The instances that timed out were generating a large report about 55k rows and looking up a lot of data from Shopify but I still need that size report to be generated for my customers
Queue trigger 😊
Worker name pimsical-stock-take-app-consumers-reports
queue consumer...
yeah you're gonna be hitting the 15 min wall time limit I bet
https://developers.cloudflare.com/workers/platform/limits/#worker-limits
I recently learned this is a thing myself by hitting it :LuL:
If you don't see 15 mins of CPU time in your metrics, it'll be this
Ah I see, is that an limit able to increased? I'm on the paid plan too
Thanks for looking into this so quickly too btw
I've got some query improvements I can do but it still could happen so I'd like to be confident I've got headroom 😅
it is not able to increase no
I think you'll need to just do less per queue invocation
🙈 Ah okay, I'll see what I can squeeze out the database
Do you know if there's any plans to increase this in future? 🙏
Not that I'm aware of currently
Ah okay, thank you 😁
@Walshy | Deploying is there a nice way to profile this? I've had it happen again, where it wasn't huge amounts of data so wondering if there's a bug.
As I'm seeing much difference with local performance, wondering if there's a nice way to do it
Cloudflare Docs
Profiling CPU usage | Cloudflare Workers docs
Learn how to profile CPU usage and ensure CPU-time per request stays under Workers limits
@Walshy | Deploying i did the profiling on one of the requests where I exceeded CPU limit but looking at the numbers here it doesn't look like it should have. The gap in the middle is pagianting through an API endpoint then couple loops to aggregate the data 🤔
Am I missing something? 🤔 Sorry to bother you
But pretty lost in the weeds at this point 🙈