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

mimir-querier needs a lot of resources #3687

Open
QuantumEnigmaa opened this issue Sep 25, 2024 · 1 comment
Open

mimir-querier needs a lot of resources #3687

QuantumEnigmaa opened this issue Sep 25, 2024 · 1 comment

Comments

@QuantumEnigmaa
Copy link

QuantumEnigmaa commented Sep 25, 2024

Lately, we've been continuously paged by the MimirHPAReachedMaxReplicas alert, mostly for the querier component. Currently this component has a maxReplicas number of 10 with its hpa and a default resources requests of 100m for CPU and 500Mi for the memory.

According to the following per-pod resources usage, CPU is fine but memory could use a little increase :
Image

From our current understanding, the querier needs to scale whenever someone uses its installation's grafana, which would mean that it should scale down during the night. Because of this, I would advocate to increase the maxReplicas to 15 and slightly increase its default memory requests in the shared-configs repo (i;e something like 650~700Mi) to avoid having to increase the former forever.

@hervenicol
Copy link

Looks like the RAM usage is quite stable over time, as you can see over 10 days here:
Image

I've increased its RAM reservations to 1GB on a few installations:

  • alba
  • alligator
  • armadillo
  • avocet
  • wallaby

Let's see in a while if it stabilises at 512MB or if it grows up to 1GB.

We could also do a bit of profiling (with pprof) to try to understand what uses this RAM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Inbox 📥
Development

No branches or pull requests

2 participants