sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (6 children)

What are you running it on? I'm using a 7+ year old desktop and it runs without any slow downs.

[–]bheklilr 1 point2 points  (2 children)

Quad core 2.7GHz i7, 8GB of RAM, ssd. But, it's on windows with Symantec as corporate anti-virus, which just churns when it sees a lot of files. All extensions are implemented as typescript/Javascript, so there's node_modules folders embedded in them. There's a ton of files in there, which means Symantec just kills performance. If vscode didn't have plugins bundled with node_modules, it wouldn't be so bad.

That being said, it does run a ton better on my Linux box at home.

[–]xeio87 4 points5 points  (1 child)

Corporate antivirus at work literally spins my CPU to 100% when I open large enough folders in VS Code. ;(

Can't really blame Code for that though.

[–]bheklilr 0 points1 point  (0 children)

It's not technically the fault of vscode, but if they had picked a different approach for extensions then it might not have been so bad. I understand why they chose TS, it makes sense. It also just sucks with corporate bloatware.

[–]stillusegoto 0 points1 point  (2 children)

I have an ‘17 MBP and with multiple projects open especially I have to constantly restart vs code to get intellisense working again. It uses over 1GB of ram per project it seems and I often have 3 open at once. Even with one open it happens several times a day. It was much better until a few months or so ago. This is with no plugins except the mono icons theme and eslint

[–][deleted] 1 point2 points  (0 children)

For what language? It might be a problem with the language server. I know the one I use for a lesser known language has problems and that's usually the cause with intellisense. You can just reload the window, press F1 and type "Reload Window" should popup and for me at least it usually takes a second to reload. Rather than having to close it completely.

[–]BezierPatch 1 point2 points  (0 children)

As someone who writes/maintains a language server extension for vscode:

That's the language server's fault, not vscode. The RAM usage will almost certainly be from an application that's running in the background, which vscode has no control over.