How to choose hardware for PhpStorm?

Question

Iron

I'm going to buy a normal PC for PhpStorm. Now, for example, I'm trying to make a commit, for 5k lines, the analyzer starts, and everything freezes for a couple of minutes. Opening projects takes about 5 seconds, auto-completion very often freezes for 3-5 seconds.

How would I determine what hardware I need to buy so that everything works without delays longer than 1 second? And I don’t want the commit analysis to take more than 10 seconds.

Projects are something like this:

---------------------------------------------------------------------------------------
Language                             files          blank        comment           code
---------------------------------------------------------------------------------------
PHP                                  39680         424852         468775        3261667
JavaScript                           20699         524918         618249        3019092
HTML                                  1717         230644          15091        1112235
CSS                                   3387         115350          22061         628472

The current features are:

CPU: Intel(R) Core(TM) i3-10105F CPU @ 3.70GHz (4 cores)
RAM: 16Gi
NVMe 3GB/s

Answer 1

CPU: Intel(R) Core(TM) i3-10105F CPU @ 3.70GHz (4 cores)
RAM: 16Gi
NVMe 3GB/s

commit, 5k lines

Proc 8 stream, enough operatives, instead of hard - put a fast m.2.
If you increase the performance, then the amount must be serious to see a real difference between the old and new setup (you have a good setup, at the moment).
UPD:
If you really want to upgrade, it's better to take an SSD first, for example: https://www.e-katalog.ru/A-DATA-AGAMMIXS70B-2T-CS.htm , test the current (good) setup, and after ( if it's a bad ass-chew) - update everything that is not nailed down.

Answer 2

Perhaps the emphasis is not on hardware, but on the size of the project and / or on the history itself in the gita.
To begin with, you can adjust the analyzer, remove unnecessary checks.
And the GIT repository can be optimized, but that's another story ( 1 , 2 )
Probably, in a storm, you can configure exclude for some folders.
Try disabling different plugins, some can greatly affect the responsiveness of the autocomplete.

Answer 3

With such characteristics of iron, the storm should not slow down so much. I would first look at the storm logs and look for where and what worries him. Maybe some plugins, maybe something is wrong in the settings. It is hard to say.
Of the general advice, we can only recommend increasing the maximum heap size. If the project is very large, then it can consume all available memory.
In general, jb has very good technical support. It is worth writing to them immediately with such questions. They answer pretty quickly.

Answer 4

A couple of minutes of analysis for a commit of 5k lines is kind of the norm.
At least you can turn it off
. But the speed of the autocomplete is confusing.
Have you tried clearing caches and reinstalling?