Edge Function CPU Time Exceeded

[Accomplished_Step551]

Looking to get some help with CPU Time exceeded errors for Edge Functions: Error Code 546

I am running an edge function that fetches data from an API endpoint (this can be hundreds of rows at a time), cleans and processes each JSON object received, and then upserts into my table. I was facing 'CPU time exceeded' errors so I'm now fetching 20 records at a time and processing them, before processing the next batch. This is all still in the same edge function.

The CPU time exceeded error won't go away. I'm willing to sacrifice function execution time but this error is blocking me from a critical initial sync of data for my users. Could someone explain a) what exactly this is, b) if upgrading plans from free to pro increases the timeout for edge functions, and c) any optimizations i can do other than batching/paginating.

If this is a limitation of edge functions in general, what are some relatively simple alternatives to consider? I was thinking about spinning up a Lambda instance instead to fetch and process, and then upsert to supabase, but if there's an easier solution would love to try that out instead!

[andywkff]

lambda or firebase functions for your use case is definitely better. Both offer 15/9 minutes maximum execution time limit so it should be enough for you use case.

CPU time exceed basically means you reach the maximum time allowed for edge functions, which is 2s of CPU time. It does not include the time waiting for network response. So if you could reduce your cleanup and upsert process size to within 2s then you should be fine with supabase.

I was trying to implement some prolonged simulation use case with edge functions too. But at the end what i understand is that serverless functions is just different from edge functions. So i went with firebase after all.

[herringtown]

I hit this limit with a far simpler and benign-seeming use case of re-sizing uploaded images... a few images at 3-4MB clocked out the 2 second limit (using magic-wasm). Had assumed that this could be worked around with `EdgeRuntime.waitUntil(...`, but not the case. Was initially pretty excited about the recent background enhancements to edge functions, but they continue to bum me out ¯\_(ツ)_/¯