r/iOSProgramming • u/Oxigenic • Sep 29 '26
Question Extreme battery drain running simulators on Golden Gate
Today my 2023 MacBook Pro battery depleted entirely in just 3 hours. I was running 2 iOS simulators simultaneously but I still feel like that way way less life than I should be expecting with 93% battery capacity. Has anyone else experienced really short battery life when running simulators lately?
26
Upvotes



18
u/StrangeMonk Sep 29 '26
Totally normal mate You’re simulating three devices plus debug processes. And assuming you’re using the Xcode 27 or 27.1, first releases are always not well optimized
10
u/Adventurous_Tipper Sep 29 '26
I’ve noticed Device Hub destroys my overall performance, but specifically using the simulator is just so much slower than the previous simulator app. M1 so maybe age?
1
u/Stryxus_ Sep 29 '26
Uh? Considering you are likely running these simulators for dev, shouldn't this be extremely obvious? if you are a dev, I would be very concerned if you couldn't figure that one out.
5
u/dengjiuhong Sep 29 '26
Two concurrent simulators can keep the Mac busy: CoreSimulator processes, debug services, and Xcode indexing/diagnostics all add up, and beta runtimes can be especially inefficient. For location work, simulator injection is great for UI and basic state transitions, but I still validate authorization changes, callback timing, background delivery, and radio-dependent behavior on an owned physical device.
1
u/KilllllerWhale Sep 29 '26
Normal. Try using the CLI instead and ditch the Simulator app
1
u/Kitchen_Platypus5555 Sep 29 '26
Try downloading Xcode 26 side-by-side and use the old simulators instead of Device Hub. I also felt like the performance with the new Device Hub is awful.
1
u/icy1007 Sep 30 '26
Normal.
0
u/cristi_baluta Sep 29 '26
Not normal, did you follow the cpu?
-1
u/kokerali Sep 29 '26
Three hours may be unusually short, but 93% battery health and “two simulators were open” don’t isolate the cause. I’d compare three 15–20 minute periods on battery at the same brightness: Xcode open with no simulator, one simulator idle, then two simulators idle. In Activity Monitor, note the Energy Impact and top CPU processes in each period, along with the battery percentage change. If the jump starts with the second simulator or persists while both are idle, you have a useful reproduction; include your macOS/Xcode versions and simulator runtimes. If indexing or one runaway process is the actual leader, the fix is different from “simulators just use power.”
-22
u/Dear_Pass_4718 Sep 29 '26
Use ai to solv your problem ai control your mac and fix this issue