Where the bottleneck is
A forge admin sees in one sentence what limits the forge now, then one row each for the internet
connection, CPU, checks, crew, memory and disk: the reading, its ceiling, and the setting that moves
it. Two doors, one reading (readBottleneck):
- Page:
/system/bottleneck, linked from/system. - MCP: the
systemtool withkind: bottleneck; a non-admin getsforbidden.
- The sentence names the row at 90% or more of its ceiling, the nearest first; else "Nothing is
at its limit."
- The connection's ceiling is the megabits a second it carries out: start the forge with
FORGE_LINE_MBIT. Unset, the row says so and never takes the sentence. Loopback is not counted.
Nothing in the forge moves this row, so it has no setting beside it.
- CPU is the machine's busy share times its cores, against the forge's own core limit when it has one.
- Not measured here, and listed on the page rather than guessed: round trips to outside hosts, a
page through the public address against loopback, bytes split by sender, and the host's traffic shaping.
Code: src/system/bottleneck.ts, src/web/pages/bottleneck.ts.