A VS Code user account described checking startup time per extension with Show Running Extensions and CPU and memory usage with Open Process Explorer. Of 40 installed extensions, six created separate processes and some took more than 500 milliseconds to start; related memory use exceeded 1.2GB even without opening a file. These were observations from that particular environment. Removing unused features and duplicate extensions improved responsiveness, but resource use by an extension host shared by multiple extensions should not be mistaken for an individual extension’s consumption.
Back to Tech
Diagnosing VS Code extensions starts with startup time and resource use
Measure before removing suspected slow extensions, then retain the tools each workspace actually needs.