Overview of the requested feature
Right now the runner's speed always follows CPU usage. It would be useful to be able to pick which metric drives it instead — for example memory, so people can watch whichever number actually matters for the way they work.
The RunCat 365 Windows version already added a "Speed based on" setting like this, so the behavior and the wording are already decided over there. This is mostly about bringing the same choice to Neo.
CPU would stay the default, so nothing changes unless someone goes in and picks something else. If GPU load isn't something the app can read on macOS, leaving it out and offering just CPU and memory would still be worth having.
Why this feature is worth the maintenance cost
Different people are waiting on different things. Someone rendering video and someone running a lot of apps at once are watching completely different numbers, and right now only the first group gets a runner that means anything to them.
The cost looks small because the app already measures these metrics for the menu bar panel — nothing new has to be collected. It's a setting that decides which existing number feeds the speed, plus one picker in settings. And since CPU stays the default, anyone who never opens that setting sees no change at all.
Related Issues (optional)
No response
Check List
Overview of the requested feature
Right now the runner's speed always follows CPU usage. It would be useful to be able to pick which metric drives it instead — for example memory, so people can watch whichever number actually matters for the way they work.
The RunCat 365 Windows version already added a "Speed based on" setting like this, so the behavior and the wording are already decided over there. This is mostly about bringing the same choice to Neo.
CPU would stay the default, so nothing changes unless someone goes in and picks something else. If GPU load isn't something the app can read on macOS, leaving it out and offering just CPU and memory would still be worth having.
Why this feature is worth the maintenance cost
Different people are waiting on different things. Someone rendering video and someone running a lot of apps at once are watching completely different numbers, and right now only the first group gets a runner that means anything to them.
The cost looks small because the app already measures these metrics for the menu bar panel — nothing new has to be collected. It's a setting that decides which existing number feeds the speed, plus one picker in settings. And since CPU stays the default, anyone who never opens that setting sees no change at all.
Related Issues (optional)
No response
Check List