Webstorm gets extremely slow with node.js

Does anyone know what a deal is with this IDE? I worked for a while, recently it has become very slow and non-responsive from time to time. Assembles the processor even when editing multiple js files.

Features: 1. My code base is getting bigger ... 2. I have several listeners that compile coffeescript and sass files in the background when they change.

In any case, I am very surprised (the worse) that it is so slow. Would expect better from an IDE developer.

Has anyone had such a problem before? 10x

+52
performance webstorm
Sep 10 '14 at 12:53 on
source share
3 answers

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:

+66
Apr 12 '15 at 11:42 on
source share

I was dealing with a similar situation. The processor used to spikes like crazy, and the IDE is used to lag. Go to WebStorm setup and try disabling plugins that you don't need.

For example, if your project uses SASS, what is the point of running the LESS plugin? Similarly, if your project uses Git, you do not need to have CVS or Perforce Integration.

Disable plugins you don't need

The CPU is still splashing when WebStorm indexes my project files, but I usually just wait for it.

+12
Aug 10 '16 at 9:57
source share

Now you can do it from the user interface.

enter image description here

These are mine before and after. No problem with the garbage collector. Just multiplied all the values ​​by 4. Machine: 20 GB of RAM, 4Ghz i7 CPU and SSD-drive. By default, he began to lag. Now there is no lag.

Paste as text for quick copy:

 # custom WebStorm VM options # Default: # -Xms128m # -Xmx750m # -XX:ReservedCodeCacheSize=240m # -XX:+UseCompressedOops -Xms512m -Xmx3000m -XX:ReservedCodeCacheSize=960m -XX:+UseCompressedOops 
+8
May 12 '17 at 11:31
source share



All Articles