Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Moosetwik

macrumors newbie
Original poster
Hey everyone. I've recently bought the above MacBook after using an iMac for Xcode since I started learning a month or so ago. Anyway, is it normal for Xcode to be a huge battery drain even when I'm not building or simulating apps? The average battery impact is 10.85 currently, and the estimated time remaining in activity monitor goes down to about 2-3 hours remaining on 90% with Xcode running. Is this normal, is there a setting I can use when on battery?
 
Xcode is constantly indexing and incrementally compiling etc as you code — it's a battery hog!

I get ~4-5hrs on my 15" MBP with Xcode though — have a look in the Energy tab of Activity Monitor and see if anything is triggering the discrete GPU.
 
The energy impact is primarily based on CPU load. For a two core CPU peak impact is around 400. So 10 is a fairly light load.

Look for the explanation elsewhere:
- high brightness
- externally connected equipment (display, usb disk, hub)
- other processes (spotlight, time macine, ...)
- or combination of all of these

The dgpu would normally be on the list, but as this is a ntb mbp you do not have a dgpu.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.