3 ms·
Nah, I'm running a cheap N5000 (1.10 GHz) with 4 GB of RAM at home and VScode runs well. At the end of the day, it's the extensions that might slow the editor d
by throw_m239339 6y ago
Nah, I'm running a cheap N5000 (1.10 GHz) with 4 GB of RAM at home and VScode runs well. At the end of the day, it's the extensions that might slow the editor down as they greatly vary in quality.
With only some Typescript/LESS/Node/Linting/Live Reload extensions, VSCode is sitting at 70 Mo right now. I think Microsoft did a great job with it. My machine can barely run Android Studio or Webstorm on the other hand, unless I turn off code inspection.
- raihansaputra 6y agoThat's amazing. I've been trying to profile which extensions are causing my slowdowns but still not getting a satisfactory result. I think my ESLint/Vetur is re-checking all open files on every keystroke (not debounced) and it becomes slow after a few hours of the editor being open. But I can't really get it down to a specific extension.
- jakear 6y agoHave you tried profiling the extension host?
- raihansaputra 6y agoThanks for the tip! Seems like Bracket Pair Colorizer 2 and Rainbow Indentation doesn't play nicely with the Vim extension. Bracket Pair Colorizer 1 is fine though, but I don't have a replacement yet for Rainbow Indentation.
- hevelvarik 6y agoAre you running a browser with multiple tabs, just boggles my mind how that works with 4gb. Are you using a funky light weight window manager. I truly wish to know how you manage it.