Em Sharnoff 722e5260bf vm-monitor: Don't set cgroup memory.max (#5333) ...

All it does is make postgres OOM more often (which, tbf, means we're
less likely to have e.g. compute_ctl get OOM-killed, but that tradeoff
isn't worth it).

Internally, this means removing all references to `memory.max` and the
places where we calculate or store the intended value.

As discussed in the sync earlier.

ref:

- https://neondb.slack.com/archives/C03H1K0PGKH/p1694698949252439?thread_ts=1694505575.693449&cid=C03H1K0PGKH
- https://neondb.slack.com/archives/C03H1K0PGKH/p1695049198622759

2023-09-18 17:47:48 +00:00

..

bin

compute_ctl: add vm-monitor (#4946)

2023-08-24 15:54:37 -04:00

cgroup.rs

vm-monitor: Don't set cgroup memory.max (#5333)

2023-09-18 17:47:48 +00:00

dispatcher.rs

monitor/compute_ctl: remove references to the informant (#5115)

2023-08-29 02:59:27 +03:00

filecache.rs

vm-monitor: Add flag for when file cache on disk (#5130)

2023-08-29 12:44:48 -07:00

lib.rs

vm-monitor: Don't include Args in top-level span (#5264)

2023-09-10 20:15:53 +03:00

protocol.rs

monitor/compute_ctl: remove references to the informant (#5115)

2023-08-29 02:59:27 +03:00

runner.rs

vm-monitor: Don't set cgroup memory.max (#5333)

2023-09-18 17:47:48 +00:00