Replies: 2 comments
-
Yes, I recently had to upload 90k photos to the supabase storage and each was around 100kb. My connection speed was 200mbps and the whole process took about 30+ hours which was a shock to me. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Nothing here? It's still so so slow. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there,
I've noticed, that the upload of a file (pdf file with about 70kb) from a supabase edge function to the supabase storage takes round about up to 700ms. On the client side it takes about 900 - 1000ms (custom database triggers, RLS, etc.).
The edge functions runs completely in the
service_role
context, so it bypasses any RLS, custom database triggers or further checks.The code for the server-side upload looks simplified like following:
So absolutely nothing special here.
I'm logging everything what happens in the supabase edge functions, there I noticed the high amount of time it needs to process the upload, here a few examples:
From the storage logs, I can see some additional stuff like this (simplified & summarized):
I'm explicitly calling all my edge functions with the region header to prevent any overhead of load balancers for routing. As well as re-deployed every edge function with the latest CLI version.
Something got my attention:
hostname: storage-api-lb-eu-central-1-ext.storage.supabase.com
It seems like the storage upload makes some external load balancer routing roundtrip, even if calling internally?
The avg cpu time over the last 7 days is at about 243ms, the avg memory usage at about 6.36MB.
I'd expect something about ~ 100ms for a backend side process and a file with just a few kb.
Has anyone else had the same experience or can tell me how I can improve this?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions