I can recommend you to run Cadvisor. This will give you a whole set of CPU metrics that enable you to have a more detailed insight. You will probably notice that the memory cache is the one that just keeps increasing, especially after a bunch of queries.
[email protected] schrieb am Donnerstag, 24. September 2020 um 09:46:07 UTC+2: > Thanks for your reply > Is there any way to know the maximum persistence volume , as we need to > fix a resource quota for prometheus in kubernetes. > > On Wednesday, 23 September 2020 at 20:27:50 UTC+5:30 [email protected] > wrote: > >> On 21.09.20 00:27, [email protected] wrote: >> > Memory Consumed by prometheus is keep on increasing day by day . Though >> Number >> > of Targets are same. >> >> Yes, Prometheus uses as much RAM as possible for mmap'ing, making your >> queries faster. >> >> > What is is the persistence volume of prometheus , or how we can >> evaluate the >> > same and limit our memory consumtion. >> >> You don't have to. When the OS needs the RAM, it will simply take it >> away from Prometheus. >> >> There is a certain amount of memory that Prometheus needs to exist. If >> you don't have enough for that, it will OOM. >> >> You can look at >> >> https://www.robustperception.io/how-much-ram-does-prometheus-2-x-need-for-cardinality-and-ingestion >> >> , although a lot has been optimized over the last 1.5 years since that >> article was published. >> >> -- >> Björn Rabenstein >> [PGP-ID] 0x851C3DA17D748D03 >> [email] [email protected] >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/4bbb539a-b1bb-431c-b5de-22dbcebb9450n%40googlegroups.com.
