Power Save Mode in PhpStorm
It is no secret that PhpStorm’s CPU usage can be quite high at times. This is primarily caused by various code insight features including auto-completion, syntax errors checking, intention actions and on-the-fly inspections. These processes are always running in the background and can be CPU-intensive.
When the CPU performance is a bottleneck, or if you work on a laptop without a power supply and want to get several extra hours of battery life, PhpStorm has got you covered.
Several options exist, which you can apply with the help of Hector the Inspector.
To start, click the Hector icon in the PhpStorm status bar:
By default, the highlighting level is set to Inspections, and the full range of background operations runs as you type. When you set it to Syntax, no warnings other than syntax errors will be reported, and your laptop’s CPU usage will be notably reduced:
When you set highlighting level to None, syntax errors will be ignored as well, and CPU usage will be even lower. Hector will turn his face away, and the code analysis icon in the editor’s top-right corner will be set to OFF:
Changing the highlighting level is only applied to the current file. If you work with several files, you will need to disable the inspections and syntax highlighting for each of them individually, which certainly is a tiresome task.
In this case, simply use Power Save Mode, which will disable all inspections and other CPU-intensive tasks application-wide. The PhpStorm functionality will be reduced to the one of a text editor, but you will get the most life out of your laptop battery.
To turn Power Save Mode on, click the Hector icon and select the Power Save Mode checkbox:
Note that the Hector icon fades out in the PhpStorm status bar:
As is the case with the majority of the PhpStorm’s actions, you can turn the Power Save Mode on in a matter of seconds with the keyboard. Simply invoke the Actions Search by pressing Shift+Command+A (Shift+Control+A on Windows), type ‘Power’, press Enter, and enjoy several extra hours of coding:
If enabling Power Save Mode doesn’t help, or if you simply believe that there’s something wrong about those CPU spikes, capture your CPU usage snapshot and share it with our support team as described here.
Your JetBrains PhpStorm Team
The Drive to Develop
Subscribe to Blog updates
Thanks, we've got you!
Qodana Clone Finder: Early Access Program
In December 2020, we announced the EAP for Qodana, which is rapidly evolving into a comprehensive platform that allows companies to perform multi-level evaluations of the quality of code they own, contract, or purchase. Qodana helps you detect bugs without relying on an IDE, either on a local machi…
PhpStorm 2020.2 EAP #3
The Early Access Program for PhpStorm 2020.2 is in full swing and today we’ve got the third build of the 2020.2 EAP for you. In this blog post, you can read about improvements for Git installed in WSL2 and Search Everywhere. Download PhpStorm 2020.2 EAP (more…)…
PhpStorm 2019.3.3 Preview
We’ve just rolled out a preview for the third minor update for PhpStorm 2019.3. Please give the PhpStorm 2019.3.3 Preview build 193.6494.5 a try and share your feedback with us. (more…)…
How to Upgrade to PHP 7.4 with PhpStorm
Check out our fresh video with a few nice tips and tricks on how to update your codebase to PHP 7.4. It combines materials from the PhpStorm 2019.2 and PhpStorm 2019.3 releases, with a few cool bonuses to boot. Nikita drew our attention to the fact that setters are slower than assigning prop…