Edge + Accelerate cold start
Is there coldstart with edge + accelerate?
it takes like 10 seconds for my query to get a result
is this normal?
Any way to speed it up?
13 Replies
Happy to help, but we need a bit more information
1. Where is your app deployed?
2. Are any of your queries cached?
3. Is this all queries? A specific one?
4. Could you share your github handle so our engineering team could take a closer look?
Please feel free to open a support ticket after logging in at https://cloud.prisma.io/
You can open a ticket by clicking on Support on top right side of the UI.
This will share your project details with us which would make it easier to debug the issue.
Prisma Data Platform
Provision a database for your Prisma project, browse your data with the Data Browser, test your queries with the Query Console, and solve your connection pooling issues with the Data proxy.
Unknown User•8mo ago
Message Not Public
Sign In & Join Server To View
Hey @Lexicographical 👋
Can you please let me know your GitHub handle?
If you are on a Pro/business plan then you can also directly send us an email on [email protected]
Unknown User•8mo ago
Message Not Public
Sign In & Join Server To View
I assume you are referring to Project called "Brain2"?
I am observing only 10 requests in the last 24 hours. In which region is your database MongoDB database hosted?
Unknown User•8mo ago
Message Not Public
Sign In & Join Server To View
Thanks for sharing your GitHub handle and the request id.
This issue seems to be isolated with MongoDB databases. I'll try to reproduce this on our end and investigate further 🙏
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
Same thing here.. Nextjs, mongodb and vercel. Timing out after 10 sec on my first requests/ cold starts
This is now affecting my production instance so a answer soon would be great!
@Fabrizio have you been able to work around this?
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
Hey,
This issue is likely isolated to the MongoDB connector. I have shared this with the team internally, I'll provide an update as soon as possible.
One workaround that seemed to have resolved the issue for one of the MongoDB + Accelerate user is to create a CRON that invokes a simple database query every 10-15 mins, in order to prevent Query Engine from being shut down. I am aware that this is not the most ideal workaround, but just mentioning it here in case anyone wants to try it out.
Hi @Nurul Just checking in.. have you recieved any new info on this bug?