The remote extension makes it easy to run VSCode on the frontend of the clusters, which sometimes leads to heavy Jupyter notebooks running on the login node.
Running VSCode on a compute node is not trivial, but not impossible either. See the (lengthy) discussion in this GitHub issue.
The remote extension makes it easy to run VSCode on the frontend of the clusters, which sometimes leads to heavy Jupyter notebooks running on the login node.
Running VSCode on a compute node is not trivial, but not impossible either. See the (lengthy) discussion in this [GitHub issue](https://github.com/microsoft/vscode-remote-release/issues/1722).
Furthermore, running VSCode on the frontend with many tabs open puts a heavy load on the NFS servers with one thread per file inotifywaiting the open file.
Furthermore, running VSCode on the frontend with many tabs open puts a heavy load on the NFS servers with one thread per file `inotifywait`ing the open file.
The remote extension makes it easy to run VSCode on the frontend of the clusters, which sometimes leads to heavy Jupyter notebooks running on the login node.
Running VSCode on a compute node is not trivial, but not impossible either. See the (lengthy) discussion in this GitHub issue.
Furthermore, running VSCode on the frontend with many tabs open puts a heavy load on the NFS servers with one thread per file
inotifywait
ing the open file.