Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow specifying maximum memory usage #551
Comments
beorn7
added
the
duplicate
label
Feb 23, 2015
This comment has been minimized.
This comment has been minimized.
|
See |
beorn7
closed this
Feb 23, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
matthiasr commentedFeb 23, 2015
The actual memory usage can not really be set predictably through
storage.local.memory-chunksalone. To operate a Prometheus reliably, it would me much nicer to just say "you can use this much memory". It should be able to figure out by itself what that means in terms of chunks or allocations.It would be good if this is a hard limit (including all other memory uses) but a best effort would already help a lot (together with rules of thumb on overhead).
The default should be a sensible fraction of available system memory, or some fixed number, whichever is lower.