How often NotchStar updates system stats
NotchStar’s System tab takes a new reading once a second, and only while that tab is on screen. When the notch is closed, or you are on another tool, nothing is sampled. There is no background process collecting history.
The three clocks
| Where | How often | When it runs |
|---|---|---|
| System tab: CPU, memory, disk, battery, network | Once a second | Only while the System tab is open |
| Disk tab, Monitor, Usage: busiest processes | Every 3 seconds | Only while Monitor is open |
| Disk tab, Monitor, Ports: listening ports | About every 9 seconds | Only while Monitor is open |
The ports list is refreshed on every third pass of the 3 second loop, because listing ports and reading each process’s folder costs more than reading counters.
What this means in practice
- Open the tab and the first CPU reading is 0 and the network speed shows a dash. Both need two samples, so they are real after about a second.
- NotchStar keeps no history of CPU or memory. When you close the tab, the readings are gone.
- A short spike lasting less than a second can fall between two samples.
Why it works this way
Sampling only when you can see the numbers keeps the cost near zero when you are not looking. The Disk tab goes further: a scan of caches, duplicates or large files starts only when you press its button. Read whether the System tab affects battery for the cost side.
The feature pages have the full lists: System stats and Disk. For what the Ports table shows and when it refreshes, see the Ports list columns.
