There are some regressions in v5+ as compared to v4 (see the discussion in https://github.com/nodejs/node/issues/3875#issuecomment-188729531). We didn't get any fixes from V8 team unfortunately, but workarounds included in 2016.2 (https://youtrack.jetbrains.com/issue/WEB-19117) help to improve the performance - for all projects we've tested performance is not much worse than with node 4.x. Can you provide the project that shows up the issue? Would be very helpful. For now you can try disabling js.debugger.v8.use.any.breakpoint in WebStorm registry (Help -> Find Action, type 'registry' to open it)
There are some regressions in v5+ as compared to v4 (see the discussion in https://github.com/nodejs/node/issues/3875#issuecomment-188729531). We didn't get any fixes from V8 team unfortunately, but workarounds included in 2016.2 (https://youtrack.jetbrains.com/issue/WEB-19117) help to improve the performance - for all projects we've tested performance is not much worse than with node 4.x.
Can you provide the project that shows up the issue? Would be very helpful.
For now you can try disabling
js.debugger.v8.use.any.breakpointin WebStorm registry (Help -> Find Action, type 'registry' to open it)