How it was measured
| App | NotchiDex 0.1.0, running normally since sign-in |
|---|---|
| State | Idle: the island collapsed to its small pill, no music playing, Notchi doing its usual idle blinks |
| Machine | Laptop with an AMD Ryzen 9 4900HS (8 cores, 16 threads), 15 GB usable RAM |
| Windows | Windows 11 Pro, build 26200 |
| Sampling | One reading per second for 120 seconds, using the same Windows counters Task Manager reads |
| Tool | measure-footprint.ps1 (below), read-only |
Results
Run 1 · 7 Oct 2026, 21:00
| Counter | Median | Average | Peak |
|---|---|---|---|
| Memory (Task Manager) private working set | 10.9 MB | 11.3 MB | 17.3 MB |
| Working set incl. shared Windows libraries | 27.8 MB | 27.5 MB | 38.6 MB |
| Committed memory reserved, not RAM in use | 94.5 MB | 105.0 MB | 147.8 MB |
| CPU (Task Manager) share of the whole processor | 0.05% | 0.08% | 1.7% |
| CPU, one core same thing, per single core | 0.8% | 1.2% | 27% |
Run 2 · 7 Oct 2026, 21:05
| Counter | Median | Average | Peak |
|---|---|---|---|
| Memory (Task Manager) private working set | 11.8 MB | 23.4 MB | 47.7 MB |
| Working set incl. shared Windows libraries | 26.8 MB | 58.2 MB | 116.8 MB |
| Committed memory reserved, not RAM in use | 161.0 MB | 163.5 MB | 223.4 MB |
| CPU (Task Manager) share of the whole processor | 0.05% | 0.46% | 4.8% |
| CPU, one core same thing, per single core | 0.8% | 7.4% | 77% |
Peaks are single one-second readings. Run 2 has higher averages and peaks: at one point memory rose to 48 MB, which is what happens when one of the island's views opens. We kept the run as it was instead of re-running until the numbers looked nicer. The medians match run 1.
Three memory numbers, explained
Private working set is what Task Manager shows in its Memory column: RAM that belongs to NotchiDex alone. This is the honest "how much is it using" number.
Working set adds pages shared with other programs, such as the Windows libraries every app loads. Those pages exist anyway, so they are not really NotchiDex's cost.
Committed memory is address space Windows has promised the app, mostly reserved by the .NET runtime. It is not RAM in use, which is why it is much larger and why Task Manager doesn't show it by default.
Why CPU shows 0%
Task Manager shows CPU as a share of the whole processor. NotchiDex used about 0.05% of it, which rounds to 0%. Measured against a single core it is under 1%, and that small amount is Notchi blinking and flicking its tail every few seconds, plus a light check every 30 seconds for reminders.
The rest of the time NotchiDex is asleep: it waits for Windows to announce changes (a new song, the volume, a charger, a fullscreen app) instead of asking over and over, and the island only animates while it is actually changing shape.
When it uses more
Opening Home, the shelf or the music player loads those views, so memory goes up while you use them. Once the island has been back to its small pill for about 45 seconds, NotchiDex hands the unused memory back to Windows, which is why the idle number above is so small. Dragging Notchi around or playing music with the visualizer uses a little more CPU while it happens.
Measure it yourself
The script reads the same counters as Task Manager once a second and prints a summary. It is read-only: it changes nothing, sends nothing anywhere and needs no admin rights. Download measure-footprint.ps1 and read it first, it's short.
- Leave NotchiDex running as a small pill, with no music playing.
- Open PowerShell in the folder where you saved the script.
- Run it. Windows blocks downloaded scripts by default, so this allows it for this one run only:
After two minutes it prints the median, average and peak for each number, plus your PC's processor and Windows version. Add -Seconds 60 for a shorter run, or -Json result.json to save the results.
Got different numbers? We'd love to see them: paste the summary on the feedback page. Every machine is different, and real numbers from other PCs make this page more useful.