Re:How to intentionally throttle CPU on a M1 MacBook?
by londons_explore on Monday October 31, 2022 @11:05AM
(#33406788)
Depending on what your program is, you might be able to just do some testing on a users machine.
I sometimes use a remote desktop tool (eg. teamviewer) to troubleshoot my software running on a users machine (with the user on the phone normally).
It's usually the quickest way to understand what issue a user is having, and the user walks away thinking they're getting great customer service.
It could be a good way to get a rough feeling for which areas of your software perform well/badly on a low end machine. One benefit is you get to experience it the way a user does - so the interactions with a 7 year old copy of norton antivirus, one of 13 programs running at once with 1GB of RAM, the fact the user has an always-on-top program that is blocking some of the UI but they don't know how to move it, etc.
I sometimes use a remote desktop tool (eg. teamviewer) to troubleshoot my software running on a users machine (with the user on the phone normally).
It's usually the quickest way to understand what issue a user is having, and the user walks away thinking they're getting great customer service.
It could be a good way to get a rough feeling for which areas of your software perform well/badly on a low end machine. One benefit is you get to experience it the way a user does - so the interactions with a 7 year old copy of norton antivirus, one of 13 programs running at once with 1GB of RAM, the fact the user has an always-on-top program that is blocking some of the UI but they don't know how to move it, etc.