Need to inspect what cause Postgresql compute time exceed #7596
Replies: 1 comment
-
This discussion was automatically closed because the community moved to vercel.community |
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
-
Acknowledgement
Question
I'm on a Pro Plan. I've been working on the preview environment for 7 months without problem. But lately when I deployed to the production suddenly the Postgresql reaches 75% monthly usage limit in just 2-3 days. This is unusual. All I can do is to inspect the differences between the prod and preview and try to optimize the code. But I need a tool or a more efficient way in the admin dashboard to know what exactly caused the peak compute time. For example the sql compute time stats by serverless functions.
I'd also like to ask if my recently many redeployments can be the reason? Deployment alone should not affect the sql compute time, but I use Prisma in my project, so the migration process every deployment multiplies by the number of deployments may be the reason. Yes?
Please help.
Beta Was this translation helpful? Give feedback.
All reactions