Commit 3a02d3b
export memory events high and max metrics
Summary:
Same as D93677082, these are another metrics I want to add to monitor about whether we are close to OOM, and do some test see if we can use them as extra metrics for memory shedding.
The [metrics](https://facebookmicrosites.github.io/cgroup2/docs/memory-controller.html) added are:
- **memory events high**: The number of times processes of the cgroup are throttled and routed to perform direct memory reclaim because the high memory boundary was exceeded.
- **memory events max**: The number of times the cgroup's memory usage was about to go over the max boundary -- if we see failure about reclaim after this happen, we will OOM.
For now memory.high = memory.max in Revproxy settings thus memory_events.high = memory_events.max, but we might change that for better OOM protection so I'm still going to export two metrics here.
Differential Revision: D93800675
fbshipit-source-id: eb050bff5a404d11f574694f7b0bb892667e50a21 parent e76d8a1 commit 3a02d3b
1 file changed
+16
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
168 | 168 | | |
169 | 169 | | |
170 | 170 | | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
171 | 179 | | |
172 | 180 | | |
173 | 181 | | |
| |||
367 | 375 | | |
368 | 376 | | |
369 | 377 | | |
| 378 | + | |
| 379 | + | |
| 380 | + | |
| 381 | + | |
| 382 | + | |
370 | 383 | | |
371 | 384 | | |
372 | 385 | | |
| |||
439 | 452 | | |
440 | 453 | | |
441 | 454 | | |
| 455 | + | |
| 456 | + | |
| 457 | + | |
442 | 458 | | |
443 | 459 | | |
444 | 460 | | |
| |||
0 commit comments