memory-cap: keep the header comment under the block limit
This commit is contained in:
parent
22105fe423
commit
dfe8f9eac0
1 changed files with 5 additions and 8 deletions
|
|
@ -20,14 +20,11 @@
|
||||||
# `hive-agent` and `hive-subagent-daemon` spawn `claude` as a plain child,
|
# `hive-agent` and `hive-subagent-daemon` spawn `claude` as a plain child,
|
||||||
# which inherits it, so neither unit may set or unset it.
|
# which inherits it, so neither unit may set or unset it.
|
||||||
# - `MemoryHigh=` on `hive-subagent-daemon` and on `hive-bash-daemon`, two
|
# - `MemoryHigh=` on `hive-subagent-daemon` and on `hive-bash-daemon`, two
|
||||||
# thirds of the cap each, as generator drop-ins. The subagent daemon spawns
|
# thirds of the cap each, as generator drop-ins. Each daemon's cgroup holds
|
||||||
# nested `claude` sessions as plain children, so its cgroup already is the
|
# its children (nested `claude` sessions, bash tasks), so a `cargo` or
|
||||||
# "all subagents" cgroup. The bash daemon's cgroup holds every bash task
|
# `nix build` storm throttles itself there before the container's
|
||||||
# (`tasks/<id>/`), so a `cargo` or `nix build` storm throttles itself there
|
# `MemoryMax=`. `High`, not `Max`: past it the kernel reclaims hard and the
|
||||||
# before it reaches the container's `MemoryMax=`. `High`, not `Max`: past it
|
# work slows down, so the last third stays free for the agent's own turn.
|
||||||
# the kernel reclaims hard and the work slows down, so the last third stays
|
|
||||||
# free for the agent's own turn, but a task that needs more still gets it when
|
|
||||||
# the container has memory to spare.
|
|
||||||
#
|
#
|
||||||
# Tested by `checks.script-test-agent-memory-cap` and
|
# Tested by `checks.script-test-agent-memory-cap` and
|
||||||
# `checks.module-eval-agent-memory`.
|
# `checks.module-eval-agent-memory`.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue