2

on our Linux servers we observe quite some .vscode-server processes (basically $PREFIX/.vscode-server/bin/$ID/node) from developers using the vscode-remote-ssh extension. Unfortunately these processes put considerable load onto the systems, due to waiting for I/O (state "D"/uninterruptible sleep).

All affected filesystems are NFS (v3 and v4.0) mounted shares. There's nothing we can do on the fileserver end.

  • Why exactly do these processes require so much I/O? The .vscode-server processes sometimes generate more load than some of the data processings on these servers.

  • Is this a known problem of vscode-remote-ssh and/or is there a way to solve or work around this I/O problem?

drosera
  • 41
  • 2

2 Answers2

0

I found that information from the VS Code's documentation and it helped me to solve the problem. I used the following commands:

# Kill server processes
kill -9 `ps aux | \grep vscode-server | \grep USER | \grep -v grep | awk '{print $2}'`

You as well can delete files, if they took up too much space. ! But be careful !, clearing the files will erase information about VS Code extensions, which may be useful.

# Delete related files and folder
rm -rf $HOME/.vscode-server # Or ~/.vscode-server-insiders
Andrew Shaban
  • 129
  • 2
  • 16
0

I had same problem.

It helped me:

First

I thought that some extension in vscode may cause this problem, and I deleted several of the which I never used. Some ssh remote connection but not main that can connect vscode by ssh to my server. It decrease my cpu usage by 25%.

Second

I notice that vscode always tells me about - I can't read all files on server, so I thought that vscode trying to do that on a cycle and can't stop, just trying and trying.

So I did this: https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc

It helped me completely.

K.Igor
  • 143
  • 1
  • 2
  • 10