Track used for cache memory #1240

New issue

Open

opened 2025-12-28 17:22:18 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:22:18 +00:00

Owner

Originally created by @carpawell on GitHub (Jul 16, 2024).

We often do some caching and often use "10/64/100mb cache for <something> at max is not bad" words and it is hard to understand now how many "at max" we already can have cached. Is it 1gb of memory? 100mb?

Describe the solution you'd like

Add a prometheus metric that describes memory usage (even approximate is better than nothing) by our caches. It allows understanding how much free mem we can have if set nspcc-dev/neofs-node@22259ce755/config/example/node.yaml (L75) to zero value.

Describe alternatives you've considered

Do nothing. No real requirement for making it now in fact.

Originally created by @carpawell on GitHub (Jul 16, 2024). ## Is your feature request related to a problem? Please describe. We often do some caching and often use "10/64/100mb cache for \<something\> at max is not bad" words and it is hard to understand now how many "at max" we already can have cached. Is it 1gb of memory? 100mb? ## Describe the solution you'd like Add a prometheus metric that describes memory usage (even approximate is better than nothing) by our caches. It allows understanding how much free mem we can have if set https://github.com/nspcc-dev/neofs-node/blob/22259ce755199d6e87331a3b58cc14449a36f69e/config/example/node.yaml#L75 to zero value. ## Describe alternatives you've considered Do nothing. No real requirement for making it now in fact.