commit 7318132a7c176d41f0fbb3433b5481a5074a2f59
author Edward Lee <edwarddl@google.com> Tue Sep 02 23:11:26 2025 +0000
committer mdb:gbmc-git-owners <superproject-auto-update@invalid> Thu Sep 04 15:22:14 2025 -0700
tree 344630ea7e9cff1684fd33e2cb51439c56c38c09
parent d8da05d7c1dc1c23e4890f50a37ed5837372d0e1

Set bmcweb's oom_score_adj to -200

Bmcweb is early to be killed during oom setting, we should have it only killed if it takes up an egregiously large amount of memory.

With 250MB and -200 adj, the oom score is around 640, and the average oomscore seems to be around 660.

When bmcweb gets near 300MB, it will be a target for removal.

Tested:
# echo -200 > /proc/152849/oom_score_adj
# cat /proc/152849/oom_score
643

Google-Bug-Id: 438738723
Change-Id: I24692c702f0ae7cf11599d336d1b7f313cdd9dce
Signed-off-by: Edward Lee <edwarddl@google.com>