Increase niceness (decrease priority) for vscode processes or limit the number of processes that vscode can spawn

vscode spawns a huge number of processes on the remote machine (in my case, it is a server with 96 cpu for computing). When vscode is connected to the remote, my own code (running on the remote) would become 10 times slower (literally), so I have to disconnect vscode before running my own code. However, sometimes I have to manually kill vscode processes even after I disconnect it. In my case, my code is written in python that uses multiprocessing to spawn multiple child processes, each of which use subprocess package to call an external program (written in C++) to perform calculation. I still don't know why remote connection of vscode would make my code slower. When I check the processes running in the background, I find tons of vscode processes. I guess it may be the reason why my code would become slower when vscode is connected. Therefore, I think it should be helpful to limit the number of processes vscode can use or increase the niceness of vscode-remote.

Btw, I think it is important to have an option to kill all vscode related threads automatically on the remote machine upon disconnection.

No repository file, test, or entry point is named. Start by reproducing the slowdown during a VS Code remote session and inspecting the remote process tree, including behavior after disconnection. Done would require a clearly chosen, tested mechanism for limiting or lowering VS Code process priority or cleaning up its remote processes.