Although Macs are great at managing their energy use which allows MacBooks to maximise the time they are able to run from battery power alone, there are situations in which you may wish to extend their energy efficiency even more.
The Intel CPU running in your Mac that’s the i number usually from i3 through i9 in the current Mac line-up supports [Intel Turbo Boost which accelerates processor and graphics performance for peak loads, automatically allowing processor cores to run faster than the rated operating frequency.
Intel Turbo Boost, unlike manually overclocking a processor, is designed to avoid overheating by throttling the performance (speed) of the processor when the temperature gets too high.
You can see the current base speed of your processor by going to Apple Menu > About This Mac:
On this Mac we can see the processor base speed is 3.69 Ghz, and if we go to https://everymac.com and search for the Mac Pro (Late 2013) we can see on its stats page the processor in the Mac supports a Turbo Speed of 3.9Ghz.
If you like to track your Macs and their specs there is also a nice little app available in the App Store called Mac Tracker.
When Intel Turbo Boost Technology kicks in and your processor starts running at the higher clock speed your Mac will start to consume more power, naturally if this is on a MacBook and you are not plugged into a charger then your battery life will be shortened.
If you don’t need this automatic power increase and would like to extend your battery life there is a great App called Turbo Boost Switcher which you can use to limit the Turbo Boost technology universally. In testing I saw a 10% saving in power usage on my MacBook which could equate to an additional 1 hour of battery life.
Using the web and word processing I saw no impact on performance, while playing games and using iMovie disabling Turbo boost made my MacBook noticeably slower.
How to use Turbo Boost Switcher
I’m using the free version in this tutorial however I’d recommend purchasing the Pro version if you find the free version useful as it has the extra features:
- Auto modes based on fan speed, battery status, apps running and more!
- Fully customizable status bar
- Enter root password just once
- Auto disable Turbo Boost when not charging
- OSX Notifications integration
- Display Temps on ºC and ºF
- Free updates forever
After installing the app which is available here a new menu item will be added to the top right of the screen:
Clicking on this menu will open up the Turbo Switcher App which allows you to enable and disable the Turbo mode of your intel CPU, as well as monitor CPU load, fan speed if available & the temperature of the CPU.
The option to “Disable Turbo Boost” is the main option of the app and doing so will save on power usage.
You can monitor the power savings in the “Charts…” menu:
So, there you have it, enjoy saving around 10% power usage when the turbo mode would normally kick in, however do remember if you are using power intensive Apps or Games you may want tore-enable Turbo mode so you don’t get any stuttering or slowing of your Mac.
If you want to take your energy saving even further check out our article on keeping your Mac cool using Macs fan control here: https://grovetech.co/blog/keep-cool/
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.05 · Low AI Influence
Summary
This article discusses how to extend the energy efficiency of MacBooks by disabling Intel Turbo Boost technology using the Turbo Boost Switcher app.
Related Posts
Setting up Ollama on macOS
Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.
