You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the site hasn't loaded a Topic for anyone in longer than ~5 minutes, the next person to view a Topic will experience a loading time of several seconds. This is annoying.
I also suspect this is a reason for Google's failure to index some pages (examples that failed to index - public to view but requires logging into Google), and if this is true, then SEO is probably impacted too.
To Reproduce
No response
Expected behavior
No response
Additional context
No response
Technical ideas
I think it's highly likely that this is due to cold starts. If I remember correctly, I previously confirmed that our neon's postgres db has a cold start of < 1s. But I had a hard time nailing down Netlify's function cold start timings.
I suspect the issue is Netlify's cold starts taking too long when combined with Prisma. Would be good if we could confirm that, then look into fixing it.
The text was updated successfully, but these errors were encountered:
Describe the bug
If the site hasn't loaded a Topic for anyone in longer than ~5 minutes, the next person to view a Topic will experience a loading time of several seconds. This is annoying.
I also suspect this is a reason for Google's failure to index some pages (examples that failed to index - public to view but requires logging into Google), and if this is true, then SEO is probably impacted too.
To Reproduce
No response
Expected behavior
No response
Additional context
No response
Technical ideas
I think it's highly likely that this is due to cold starts. If I remember correctly, I previously confirmed that our neon's postgres db has a cold start of < 1s. But I had a hard time nailing down Netlify's function cold start timings.
I suspect the issue is Netlify's cold starts taking too long when combined with Prisma. Would be good if we could confirm that, then look into fixing it.
The text was updated successfully, but these errors were encountered: