Skip to content

docs: cross-reference hosted CPU capping from APP_ISOLATION.md #287

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

Open
onel wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: cross-reference hosted CPU capping from APP_ISOLATION.md #287

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
2 changes: 2 additions & 0 deletions docs/specs/APP_ISOLATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,8 @@ Used for:

Apps run with **no cgroup cap by default** and may burst above their recommendation. Peaks should complete fast, not be throttled. CPU in particular is **never capped** — it's time-shared, so a CPU-hungry app simply runs slower and harms nothing; throttling it only makes it feel needlessly sluggish.

> **Hosted profile exception.** On the hosted (cloud) profile, CPU *is* capped per instance. See `ENVIRONMENT.md` # Per-instance resource limits for the hosted profile's cgroup CPU capping.

### Control-plane protection (structural, not a cap)

"Default unlimited" leaves one hole: a runaway app exhausting RAM could trip the kernel OOM-killer and take down the *brain*, removing the very UI the user needs to fix it. Closed structurally, independent of any app limit:
Expand Down