Docs

Performance

NOBLE is meant to stay open all day, on a laptop, on battery. It uses about 22 MB of RAM, an idle terminal tab costs about 0.05% of one core and the Home screen about 0.4%.

No fixed frame rate

NOBLE redraws when an event changes something visible, at most 60 times a second under heavy output. An idle terminal redraws once a minute, Home once a second.

Work follows the screen

WhatWhen
System sensorsEvery second on the System screen and on Home (every 2 s on battery), every 5 s elsewhere.
Git statusWhen a command finishes, when Home opens, or when a repository changes.
AI quotaOnly while Home is open.
Listening portsOnly while Home is open: every 10 s, or every 30 s on battery.
Pull request and CIOnly while Home is open, for the selected project: at most every 60 s (180 s on battery), or at once when its branch changed.
Claude background sessionsOnly while Home is open and a claude launcher is installed: about once a minute (every 3 minutes on battery).
Update checkOnce a day, in the background. Off with check_updates = false.
On batteryThe Home clock drops its seconds and the blinking colon.

Measure it yourself

The repository has an idle benchmark that runs the real binary and reports CPU milliseconds per minute:

shell
$ cargo test --release --test e2e idle -- --ignored --nocapture

And a throughput test that pushes 50,000 lines of output through a pane:

shell
$ cargo test --release --test render heavy_output -- --ignored --nocapture