There are several performance improvements that you can apply to Webstorm to see if your situation improves. When my colleagues and I discovered that Webstorm was slowing these settings down, all of our problems were resolved.
First of all, make sure that your project is configured to use webstorm resources efficiently by excluding certain directories from the project. This ensures that the containing files are not indexed in memory and will not reduce performance when performing functions such as searching for files or text inside files. Some examples of good candidates for exclusion are the node_modules directory and compiled code directories.
If you have performance issues, try the following:
If you use Windows by default, you will use the 32-bit version. Go to the Webstorm directory (inside the program files) and you will see webstorm64.exe , which will run Webstorm in 64-bit mode. (You can install the corresponding 64-bit JDK ).
The default VM settings for IntelliJ IDEA may not be optimal if your project contains more than 10,000 classes, and developers often try to change the default settings to minimize the response time of IntelliJ IDEA.
You might try to run into JVM memory limits for Webstorm. Open the virtual machine settings using IDE_HOME\bin\<product>[bits][.exe].vmoptions . First try doubling the memory values ββof Xms and Xms .
Note that very large Xmx and Xms are not so good. In this case, GarbageCollector should work with most of the memory at a time and cause significant freezes.
For more information on configuring JVM memory, see:
Andrew Apr 12 '15 at 11:42 on 2015-04-12 11:42
source share