S1 #11: the System Monitor's design round (Q117-Q127)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
2026-10-06 01:04:41 +02:00
parent 00f69e8d53
commit 1df94b684a
1 changed files with 20 additions and 0 deletions
@@ -59,3 +59,23 @@ The network is 10.39.39.0/24, gateway 10.39.39.1; DHCP gives 10.39.39.1 as DNS a
 3. **Wi-Fi Service:** apply it when joining; DNS and NTP; `wifi status` and the console commands.
 4. **Settings:** the network page, the DNS and NTP rows, connection details.
 5. **Tests on the device**, recorded here.
 ## System Monitor (issue #11)
 Every milestone so far was driven by measurements, heap floors, stack sizes, TLS dips, that needed a Debug Build and a computer. The System App shows them on the device, in any build.
 ### Decisions (design round 2026-10-06)
 | # | Decision |
 |---|---|
 | Q117 | An App of its own, **System**, in release builds too. Read-only. |
 | Q118 | Four views, switched with Tab: **Overview** (CPU per core, memory, network, battery), **Tasks**, **Memory**, **System**. |
 | Q119 | Sampled once a second. A task's share is its run time over the last second; a core's load is 100 % minus its idle task's share. |
 | Q120 | **History only while the App is open:** two minutes at one sample a second, about 1 KB. The system already keeps what matters afterwards: the lowest free heap since boot and each task's lowest free stack. |
 | Q121 | **Bytes are counted per service:** IRC, Gemini, the Debug Console and Firmware Updates add what they read and write to a shared counter. The network view shows the connection details, each service's bytes in and out, and the signal strength. |
 | Q122 | Tasks: name, core, share, state and lowest free stack, sorted by share; `s` cycles the sort (share, stack, name). **Under 512 bytes of stack left shows in the warning colour.** |
 | Q123 | Memory: free heap, lowest since boot, largest free block, and a two-minute graph of free heap **with the floors of Q86 drawn as lines** (55, 40 and 20 KB). |
 | Q124 | System: uptime and why it last started, firmware and both app slots, chip temperature and CPU frequency, battery voltage and percentage, SD usage and write faults, the radio's and the GNSS receiver's state. |
 | Q125 | `info` and `tasks` are split into a **snapshot** that the console and the App share; the arithmetic (shares from two samples, sorting, the stack warning) is host-tested. |
 | Q126 | Left out: acting on tasks, an event log, exporting snapshots to the card. |
 | Q127 | The main loop uses about 81 % of a core. The App shows it; fixing it is issue #40, not part of #11. |