Skip to content

Raise the memory ceiling again: 768M was still throttling #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lbesecker195 merged 1 commit into from
Sep 24, 2026
Merged

Raise the memory ceiling again: 768M was still throttling #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions deploy/mcp-registry.service
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,18 @@ RestartSec=5
# headroom -- enough that loading the geo-IP database pushed the BEAM through
# MemoryHigh into MemoryMax and stalled every database-backed request while
# routes touching no database kept answering.
MemoryHigh=768M
MemoryMax=1G
#
# Raised again the same day. 768M was still too tight: with the geo database
# resident the working set settles near 700 MB, and memory.events recorded
# tens of thousands of `high` breaches -- the kernel reclaiming hard, which is
# the same stall in miniature. Read that file before trusting a ceiling here:
#
# cat /sys/fs/cgroup/system.slice/mcp-registry.service/memory.events
#
# `high` should stay at or near zero. It is the early warning that `max` and
# an outage are next.
MemoryHigh=2G
MemoryMax=3G
LimitNOFILE=65536
NoNewPrivileges=true
ProtectSystem=full
Expand Down
Loading