Over 61 minutes of ordinary work, ChainYourMac 2.4.7 used 67 MB of memory and 1.73% of one CPU core on average, for its two processes together. In 30% of the minutes it stayed under 1% of a core. It only does work when windows change or you move around the strip.
How much memory, CPU and battery ChainYourMac uses
Measured over 61 minutes of real work, not a benchmark. Here is what ChainYourMac 2.4.7 costs your Mac, minute by minute, and how to check it yourself in Activity Monitor.
CPU, minute by minute
Each point is one minute: the share of one CPU core that ChainYourMac's two processes used together. The engine works whenever a window opens, closes, moves or changes its title, and rests when nothing changes, so the line follows what was happening on screen. The busiest minute reached 2.9%; the typical (median) minute was 1.9%.
Memory over the same session
Memory is the physical footprint, the figure Activity Monitor shows in its Memory column. It stayed between 63 MB and 70 MB for the whole run.
Both processes, one by one
ChainYourMac runs as two processes. ChainYourMac is the app you see: the menu bar item and the settings window. PaneruHelper is the window engine, written in Rust, which moves and resizes windows and handles the shortcuts.
| Process | Memory, avg | Memory, peak | CPU, avg | CPU, busiest minute | Energy Impact, avg | Idle wake-ups / min |
|---|---|---|---|---|---|---|
| ChainYourMac (menu bar + settings) | 42 MB | 42 MB | <0.1% | <0.1% | 0 | 0 |
| PaneruHelper (window engine) | 25 MB | 28 MB | 1.67% | 2.9% | 1.7 | 27 |
How we measured
- Mac: MacBook Pro, Apple M4 Pro, 24 GB memory, macOS 26.5. 1 display (4K), 9 apps open at the start.
- App: ChainYourMac 2.4.7, the public release.
- Session: 61 minutes on November 12, 2026, during a normal working session on the developer's own Mac. No synthetic load and no benchmark script.
- Method: macOS's own
topsampled both processes once a minute: CPU over that minute, memory footprint, Energy Impact and idle wake-ups. The overall CPU average comes from each process's total CPU time at the start and end of the run.
This is one Mac and one session. More windows, more displays and lots of swiping mean more work for the engine, so your numbers will differ. Check your own Mac with the steps below.
Check it on your own Mac
- Open Activity Monitor (press ⌘Space and type “Activity Monitor”).
- Type ChainYourMac in the search field, then try PaneruHelper. Those are the two processes.
- Read the CPU tab (% CPU), the Memory tab (Memory) and the Energy tab (Energy Impact, and 12 hr Power once it has run a while).
Or watch it minute by minute in Terminal, the same way this page was measured:
top -s 60 -stats pid,command,cpu,mem,power -pid $(pgrep -x ChainYourMac) -pid $(pgrep -x PaneruHelper)
Why it stays light
- The engine waits for events. PaneruHelper reacts when macOS reports a window change or you press a shortcut, then goes back to sleep.
- Animation runs only while windows move. A scroll or a resize takes a moment of CPU, and nothing runs between them.
- No web runtime. The app is native SwiftUI with a Rust engine. There is no Electron or web view in it.
FAQ
How much RAM does ChainYourMac use?
About 67 MB for both processes together in our measurement (42 MB for the app and 25 MB for the PaneruHelper window engine), measured as physical footprint, the number Activity Monitor shows.
Does ChainYourMac drain the battery?
It's light on energy. Its average Energy Impact was 1.7, measured with Activity Monitor's own metric, and it averaged 1.73% of one CPU core. Most of the time it's idle, waiting for a window to change. It uses more energy for a moment while you swipe or windows animate.
Why are there two ChainYourMac processes in Activity Monitor?
ChainYourMac is the app: the menu bar item and the settings window. PaneruHelper is the window engine, a separate Rust process that moves windows and handles shortcuts. Keeping them apart means the settings window can be closed while the engine keeps running.
Is ChainYourMac lighter than yabai or AeroSpace?
We haven't measured them side by side, so we won't claim either way. They are all small, native-code processes. To compare on your own Mac, use the same Activity Monitor steps on this page.