Supabase
|
is there a definitive timeout for edge functions? i haven't been able to find much documentation except for this reddit post I'm triggering (via HTTP request) a Python 3.9 runtime Google Cloud Function from an edge function, but it can run anywhere from 5s - 4 min (probably more) depending on the user's input. |
Replies: 6 comments 8 replies
|
I too am confused by what's stated. https://deno.com/deploy/docs/pricing-and-limits This page mentions 10ms (or 50s) per request, but in my experience a function can run for several seconds, the post says "minutes." So not sure how to make sense of that. My function is pure and receives all it's data directly. It's run for 7-ish seconds before being stopped by free-tier limits. Possibly its about the difference between CPU time and wall clock time. What confuses me is that my function is pure. So I don't know why there'd be any disparity between CPU time and wall clock time (e.g. what's it waiting on?). |
|
It is currently 100ms of compute time (CPU time), but we don't have a determined set for wall time. Essentially the timeout in those cases comes from the service where we deployed the functions. We are working to improve this experience with more customized options in the future. The only way to tweak this at the moment is by self-hosting the Edge Functions. |
|
Firebase / Google Cloud Functions seem to only measure in wall time from all resources I can find for their timeouts. Having a hard time comparing / knowing if my existing Firebase Cloud Functions (that have a wall time of 10-15 seconds) would work with Supabase, but I want to make my next product there 🤔 |
|
Any news on that? I would also be very interested to be able to increase the CPU time limit. I have an Edge function that was working before which does generate a PDF report, but now the reports that I need to generate are bigger thus it often not works anymore. |
|
How do you tweak it when self-hosting? Is there a config file somewhere? |
|
It would be nice if that time could be controlled by devs if only so that they can easily identify whether increasing it solves a problem. Obviously, if it does, they'll have to optimize the function to bring the time down, but it does provide a way to slide by with an inefficient computation for a time, even if at added cost. |
|
My function fails when uploading files with 9+ MBs. took me some time to figure that this was the problem as the crash error message was not explanatory. |
|
is 100ms still actual? |
|
Yes, it's still 100 ms for CPU time. For edge function run time, I don't know the limit. |
|
Is there a wall time limit? I have a function which uses around 8ms of CPU but takes well over 2 minutes of wall time. Would it cause problems? |
|
We documented the limits on this page:
https://supabase.com/docs/guides/functions/debugging#limitations
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Burak Can ***@***.***>
Sent: Saturday, March 9, 2024 9:42:43 AM
To: supabase/supabase ***@***.***>
Cc: Rodrigo Mansueli ***@***.***>; State change ***@***.***>
Subject: Re: [supabase/supabase] edge function timeout, a definitive answer? (Discussion #13837)
Is there a wall time limit? I have a function which uses around 8ms of CPU but takes well over 2 minutes of wall time. Would it cause problems?
—
Reply to this email directly, view it on GitHub<#13837 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGNTECBKYRODO6J24THKU3YXL7UHAVCNFSM6AAAAAAXERQIJ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DOMRZGEYDI>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
If I am self-hosting Supabase (with Supabase Edge Functions Runtime), then can the max execution time be configured in |
|
Updated link here: https://supabase.com/docs/guides/functions/limits - Old one gives a 404 |
Please, also make it clear the file upload limit with Functions. |
It is currently 100ms of compute time (CPU time), but we don't have a determined set for wall time.
Essentially the timeout in those cases comes from the service where we deployed the functions. We are working to improve this experience with more customized options in the future.
The only way to tweak this at the moment is by self-hosting the Edge Functions.