ThermaSolve on macOS: When Low Power Mode Quietly Wrecks Performance
I’m writing this as a troubleshooting log, not a review. Just a record of what happened on my Mac and what finally made the tool behave.
Day 0: what I wanted to do
I wanted to run ThermaSolve (app) locally to test a small thermal model export a colleague sent me. Nothing exotic. Open the app, load the project, verify the output, move on. This was on a MacBook Pro with an M2 Pro, macOS Sonoma 14.2, clean user profile, no weird system tweaks.
I’d bookmarked the tool earlier as part of a small OrchardKit-curated list of engineering utilities, so expectations were reasonable. Download, drag to Applications, launch.
That’s where things started getting quiet.
What broke (or didn’t, technically)
The app launched. No crash. No warning. UI appeared normally.
But the moment I loaded a project, performance dropped off a cliff. CPU usage spiked briefly, then the app became unresponsive. Beachball for 10–15 seconds, UI updates lagging behind clicks, fans spinning up for no obvious reason. Eventually it recovered, but every interaction after that felt like wading through syrup.
No error dialogs. No logs surfaced automatically. Just “working, but badly.”
At first glance, this looked like a performance bug or an inefficient build. That assumption cost me about half an hour.
Attempt #1: blame the model
My first instinct was that the input data was the problem. Maybe the project was malformed or heavier than expected.
I tried a smaller sample model. Same behavior. Tried opening an empty workspace. Still sluggish once any computation kicked in.
That ruled out the data. The slowdown was systemic.
Dead end.
Attempt #2: reinstall and reboot (the ritual)
I reinstalled the app. Cleared its support files from ~/Library/Application Support. Rebooted the system (because sometimes macOS just needs a nap).
No change. Performance degradation showed up again as soon as the tool did any real work.
Activity Monitor showed something interesting though: CPU usage wasn’t actually that high after the initial spike. The app just wasn’t being scheduled aggressively.
That was the first real clue.
Attempt #3: Energy and security throttling
macOS has a habit of quietly throttling apps it doesn’t fully trust, especially ones downloaded outside the App Store and not properly notarized. This doesn’t always show up as a warning — sometimes it just manifests as poor performance.
I checked Gatekeeper status and code signing. The app wasn’t notarized. Not blocked, but not exactly welcomed either.
Apple explains how Gatekeeper and notarization affect execution behavior here:
https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac
and in more detail on the developer side:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
Still, that alone didn’t explain the extreme lag.
Then I checked Low Power Mode.
On Apple Silicon Macs, macOS can aggressively deprioritize apps when Low Power Mode is enabled — even when plugged in. And yes, it was on.
What actually worked
Turning off Low Power Mode immediately changed everything.
System Settings → Battery → Low Power Mode → Off.
Relaunched the app. Loaded the same project.
This time: no beachball, normal CPU scaling, fans stayed quiet, UI responsive. Same workload, same data, completely different behavior.
For good measure, I also added the app to Full Disk Access, just to avoid any hidden file I/O penalties. Apple’s explanation of these privacy controls is here:
https://support.apple.com/guide/mac-help/control-access-to-files-and-folders-mchld5a35146/mac
After that, performance was consistent. Not blazing fast, but predictable — which is all I wanted.
Sanity checks
I checked whether there was an App Store–distributed build, since those tend to integrate more cleanly with macOS power management. There’s an official search entry under the same name:
https://apps.apple.com/us/search?term=ThermaSolve
I didn’t switch installs, but it explained why the standalone build behaved the way it did.
While debugging, I saved this page because it helped confirm I wasn’t imagining things about how the tool was supposed to behave on macOS:
https://spaceinnonxt.com/developer/51578-thermasolve.html
What I learned (and would do next time)
The app itself wasn’t broken. The model wasn’t the issue. Reinstalling didn’t help.
macOS was quietly putting the tool in a performance penalty box.
If I were starting over, I’d do this immediately:
- Check Low Power Mode before diagnosing “slow” apps
- Verify Gatekeeper / notarization status
- Grant disk access early for compute-heavy tools
On modern macOS, performance issues aren’t always about CPU or memory. Sometimes the OS just decides an app hasn’t earned the right to run at full speed.
Once that barrier was gone, ThermaSolve behaved like a normal engineering utility should. The fix wasn’t inside the app — it was in the system settings, hiding in plain sight.
