microsoft / microsoft/vscode-remote-release
Massive performance impact on saving code
@aeschli is already working on this.
Since Nov 10, 2020.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.45.1
- Local OS Version: Win 10
- Remote OS Version: Linux/Ubuntu18
- Remote Extension/Connection Type: Docker & WSL2
Steps to Reproduce:
Editing a large Angular application with ng-serve, locally in 8-core i9 16Gb ram, on save sometimes spikes up load to unusable limits. Last time at 17-load (on that machine) found a top offender (this one)
vscode 63679 3.1 2.1 1289484 43380 ? Sl 04:05 0:14 /home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/node /home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/out/vs/server/uriTransformer.js --useHostProxy=
There is a whole list of other spawned all contributing to this load. The same situation repeats itself whether it is WSL2 or Docker.
WSL to I am using the latest insiders build on Win arm64. It is underpowered machine and often i have to use wsl --shutdown and restart as it all just dies.
This is not limited to Angular apps, same behaviour with plain NodeJS and Rust with varied folder structure and complexity
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.