Client requests to Supabase take too much time occasionally. about supabase

[saltcod]

For your last one @mubashir-zenkoders you'll want to move the createClient out of the useEffect.

[mubashir-zenkoders]

Ok, let me try and debug it in depth.

Thank you so much. I really appreciate your help. 🎩

[encima]

Ah, that one we may not be able to fully help with as it is more about NextJS behaviour. Without seeing all the code (no need to provide it!), you could:

• make sure that this not async as client components cannot be async
• try disabling strict mode to see if it helps with debugging

[mubashir-zenkoders]

My issue is exactly match to this one, but this issue is closed, that's why I created new one.

#937

[encima]

This can certainly happen, especially when Supabase is "just postgres" under the hood.

What you can check:

• Use the Logs Explorer and find out what queries are taking too long
• Check the Query Performance page in the dashboard
• Run explain analyze to understand the queries performance issues
• Then check those queries with the index advisor
• Use the CLI to run inspect commands against the DB
• Check the metrics for your DB to see if the hardware is a bottleneck (i.e. if the CPU usage is at 100% for any of these periods)

Information we would need:

• Are you querying from the same region as your project?
• Have you optimised your database at all?
• Is this from API calls or RPC or pure SQL?
• Are you connecting directly or through the pooler (Supavisor)?

[mubashir-zenkoders]

I am using Supabase js client to connect to the supabase.

supabase.from('someTable').select('*')

My database is new, just created a month ago, no production users, only my testing data is there.

My queries usually take a noticeably short amount of time (under 100ms) to respond to, but sometimes, ANY query, not just specific one, but any query randomly takes more than minute to respond. Mostly I am the only user.

This is from the supabase js client from nextjs project. I am not connected to db directly nor am I using RPC.

I have generated this report for you, as you can see usage not ver high or even high.

[encima]

Thanks, this is a start, you would need to perform the other steps as well (index_advisor and inspect in the CLI to see index usage).

It could also be how the queries are made, do you have info from the Network panel in your browser to see the max time a query takes? Removing the application, you could also make the calls in the command line to try and narrow down the cause

[encima]

Happy to help! Please feel free to post anything here if you want additional help, it will certainly help others and we can add any general advice into the docs.

[mubashir-zenkoders]

I am also getting a weird issue since the beginning when I started to use the supabase.

Somehow, supabase JS client on the browser side does not makes req to the supabase at all, but using the same code on the server side it works simply fine.

For example, in nextjs v14, on client side, following code sometimes requests the supabase backend, and sometimes doesn't make any requests at all, resulting in loading forever.

I have verified it using the network tab.

This exact same code works on the server side in the API.

This happens sometimes, sometimes, just refreshing page also fixes the issue.

useEffect(()=>{
const supabase = createClient(...)

// when added console.logs, code does not process further this statement.
const {data, error} = await supabase.from('posts').select('*').limit(20)

// handle data and error

}, [])

[Hallidayo]

Hi all, We’re going to close this one due to inactivity. Please feel free to reopen if you’re still having issues here or open a new issue.