Skip to content
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

Open
armansaa opened this issue Dec 16, 2020 · 9 comments
Open

High memory usage when idle #6352

armansaa opened this issue Dec 16, 2020 · 9 comments
Labels
support/needs-more-info Needs more details/info/repro instructions

Comments

@armansaa
Copy link

armansaa commented Dec 16, 2020

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

hasura idle

@tirumaraiselvan
Copy link
Contributor

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?

@tirumaraiselvan tirumaraiselvan added the support/needs-more-info Needs more details/info/repro instructions label Dec 18, 2020
@armansaa
Copy link
Author

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.
I have table = 306
event trigger = 28
remote schema query + mutation = 41

After restarting the pod, memory idle is 670MB

  • After 5 minutes: 709MB
  • After 10 minutes: 778MB
  • After 15 minutes: 1315MB
  • After 20 minutes: 1316MB
  • After 25 minutes: 1317MB
  • After 30 minutes: 1319MB

Now, memory idle is 1.3GB

@tirumaraiselvan
Copy link
Contributor

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 tiru@hasura.io if possible.

@tirumaraiselvan
Copy link
Contributor

Also, did anything happen between the 10th minute and 15th minute? Has the server been completely idle from launch time?

@Difrex
Copy link

Difrex commented Jan 6, 2021

@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.

@tirumaraiselvan
Copy link
Contributor

@Difrex Thanks, we did indeed make some progress with #5536 . I will update there.

Let's keep the issues separate for now as the source of memory retainment/leak is still unknown and maybe different. Having different repros (in different issues) will help in tracking better :)

@jberryman
Copy link
Collaborator

Referencing canonical memory issue #3388

@treyhuffine
Copy link

I'm experiencing this issue on 1.3.3 as well. Happy to provide any info to help debug it.

@AndresPrez
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support/needs-more-info Needs more details/info/repro instructions
Projects
None yet
Development

No branches or pull requests

6 participants