reanimator/bee
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Remove MemoryMax=3G from bee-web.service to fix OOM kill during GPU tests

Browse Source 
dcgmproftester and other GPU test subprocesses run inside the bee-web
cgroup and exceed 3G with 8 GPUs. OOM killer terminates the whole
service. No memory cap is appropriate on a LiveCD where GPU tests
legitimately use several GB.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Michael Chus
2026-04-19 18:52:41 +03:00
parent e35484013e
commit 2038489961
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
iso/overlay/etc/systemd/system/bee-web.service
View File

@@ -10,7 +10,8 @@ RestartSec=3
StandardOutput=journal
StandardError=journal
LimitMEMLOCK=infinity
MemoryMax=3G
# No MemoryMax: bee-web spawns GPU test subprocesses (dcgmproftester etc.)
# that legitimately use several GB; a cgroup limit kills them via OOM.
# Keep the web server responsive during GPU/CPU stress (children inherit nice+10
# via Setpriority in runCmdJob, but the bee-web parent stays at 0).
Nice=0