[MGNLCACHE-250] DOC: CacheMonitor performance: improve or document properly the implications Created: 07/Dec/21 Updated: 15/Mar/22 |
|
| Status: | Open |
| Project: | Cache Modules |
| Component/s: | None |
| Affects Version/s: | 5.9.4 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoR: |
Empty
|
||||||||||||
| Documentation update required: |
Yes
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
CacheMonitor mbean exposes various metrics that can be scraped by the monitoring systems such as Prometheus or DataDog. Scraping a couple of those metrics though can have some serious implications on the system's memory allocation footprint and/or performance in general:
Both of the above perform some aggregate calculations over the entries stored in cache and may accidentally cause a multitude of those to be loaded in memory just for the iterative counting purposes. Scaping those metrics should be done carefully and our documentation needs to address that. (or we can eliminate them completely, or somehow improve their performance which I doubt) |
| Comments |
| Comment by Aleksandr Pchelintcev [ 07/Dec/21 ] |