-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High memory usage when idle #6352
Comments
Is it possible for you to share the postgres schema, hasura metadata and possibly the queries that you ran before idling at the above resource usage? |
I can't share the postgres schema. After restarting the pod, memory idle is 670MB
Now, memory idle is 1.3GB |
Hi @armansaa Unfortunately, such issues are very tricky to resolve without proper reproduction for which we will need the info I asked earlier: postgres schema, hasura metadata and (if running some initial load) sample queries. You can send the info to me privately at |
Also, did anything happen between the 10th minute and 15th minute? Has the server been completely idle from launch time? |
@tirumaraiselvan can you try a database schema from this issue #5536? Because the Hasura in our installation restarts regularly - OOM. Also, the issue of memory leak is #5868. |
Referencing canonical memory issue #3388 |
I'm experiencing this issue on 1.3.3 as well. Happy to provide any info to help debug it. |
Im experiencing this issue as well on hasura/graphql-engine:v2.5.0. Schema has around 500 tables. And Hasura container idle memory usage is about 2.GiB in GKE Pod |
Hi, I'm having a problem with Hasura. Hasura consuming massive amounts of memory when idle (2.2Gb). I am using version 1.3.3
The text was updated successfully, but these errors were encountered: