Phpstorm superslow - 282.8% CPU usage

performance svn 32bit-64bit phpstorm
Marcos Lamba picture Marcos Lamba · Jul 20, 2014 · Viewed 16.3k times · Source

After working for over 5 years with Netbeans I wanted to give a try with Phpstorm suggested by a friend.

I downloaded a fresh copy of Phpstorm and imported in the IDE a fresh project. The result is TERRIBLE!

  1. Phpstorm is terribly slow during startup.
  2. Doing an SVN commit take 5 minutes and keep CPU from 182.3% to 192%.
  3. Editing a simple line of HTML like Hello World take 5 to 7 seconds just to type the first opening character "<".

Working in this situation is a disaster moreover if I'm working on a MacPro workstation with 8GB RAM with 2 Core Duo CPU.

I really don't understand what is causing the issue. I attach a screenshot. enter image description here

P.s. Netbeans on the same workstation is flying!

Thanks in advance to all help and suggestion

Answer

Matt picture Matt · Apr 24, 2017

I've been working on a large number of git branches recently, and a coworker advised me to invalidate my cache & restart PHPStorm. It seems to have worked, but be warned - you will lose your local history.

In any case, File -> Invalidate Caches / Restart solved my issue.

Related questions

SVN performance after many revisions

My project is currently using a svn repository which gains several hundred new revisions per day. The repository resides on a Win2k3-server and is served through Apache/mod_dav_svn. I now fear that over time the performance …

Read More
TortoiseSVN 1.7 extremely slow on commit and check modifications on network share

This issue is related for operations with TortoiseSVN 1.7 only and on network share only. On the dev server I have an svn working copy where I can commit something and then update on production server. Sometimes when all active sessions …

Read More
Subversion unbearably slow on Windows 7

My company is currently using TortoiseSVN 1.6.16 32-bit on Windows XP to connect via HTTPS to a VisualSVN-Server 2.1.19 running on a Windows Server 2003 residing in the same network (no proxy). We use a self-signed certificate and Kerberos authentication using windows credentials (…

Read More