Consider starting Webstorm with belownormal process priority
There have been complaints about indexing many times in the past and I can't help but wonder why you don't simply run Webstorm at "belownormal" priority from the get-go? There must be a way to do this programmatically? And it doesn't seem like you'd lose anything by doing so, since an IDE isn't exactly like a heart rate monitor in an ICU - realtime feedback isn't vital and if enough system resources are present, it'll be just as fast as with "normal".
This occurred to me because the workaround I had previously used on Windows 7 doesn't work on 10 any more - using `start /belownormal` in the shortcut. I guess I could (and probably will) come up with some script but it just seems unnecessarily tedious.
Please sign in to leave a comment.
As far as I can see from https://www.tenforums.com/tutorials/89548-set-cpu-process-priority-applications-windows-10-a.html#option4,
start "" /BelowNormalshould still work on Windows 10Interesting! Apparently, for some reason, specifying that empty title and providing the full path is required if you want to run it as administrator.
Because if you don't run it as administrator, this will work:
But contrary to W7 that didn't give me elevated command prompts inside of Webstorm, even though my user is an administrator. So it was necessary to explicitly run it as administrator. Hence the problem and my post.
Long story short: Problem resolved for me, thanks! :) (But my opinion that users shouldn't have to go through such customization just to keep their OS from stuttering while Webstorm reindexes remains ;) )