From 7705a4af5ee85e231d694a4cc39bbf87a991cdfe Mon Sep 17 00:00:00 2001 From: Andrei Date: Wed, 1 Jul 2026 14:47:01 +0100 Subject: [PATCH] docs: cross-reference hosted CPU capping from APP_ISOLATION.md Add a one-line blockquote note in APP_ISOLATION.md # Resource limits pointing to ENVIRONMENT.md # Per-instance resource limits for the hosted profile's CPU capping behavior. Closes #286. --- docs/specs/APP_ISOLATION.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/specs/APP_ISOLATION.md b/docs/specs/APP_ISOLATION.md index c10e4776..7349582f 100644 --- a/docs/specs/APP_ISOLATION.md +++ b/docs/specs/APP_ISOLATION.md @@ -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: