You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Listing SSH targets is slow with big config/many hosts #2857
Create large (I have 36K lines and 7K hosts) ~/.ssh/config file with hosts
Open SSH targets tab of vscode
This is slow and takes a lot of CPU, the console outputs this: WARN UNRESPONSIVE extension host, 'ms-vscode-remote.remote-ssh' took 93% of 5265.002ms, saved PROFILE here: '/tmp/exthost-7388f2.cpuprofile' (the profile contains internal data so I'd rather not upload it, but it should be easy to reproduce with dummy hosts).
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A
Kind of related, it would be good to have a filtering mechanism for when you have many hosts.
Reacted by Ian Chamberlain, Ramy Elkest, Minliang Lin, Youngwan Kwon and LunarLanding
I noticed the same issue, it renders the SSH targets tab pretty much unusable in my case, unfortunately I cannot upload a profile for the same reason. In my case I have a 33-line config with ~10 hosts which Includes another 93K line file with ~12K hosts in it.
One thing I noticed however was that downgrading to version 0.49.0 of the extension allows me to actually use the SSH hosts tab again, but I can reliably reproduce with newer version of the extension Remote - SSH extension and no other extensions enabled.
This is still an issue and one I just hit. The extension is entirely unresponsive for any simple command. I have ~150k line long sshconfig (large number of company machines) that normal ssh command works fine, but this extension struggles with.
By filtering down the config to 4 hosts, I hoped I would fix this drag.
However, the extension still takes multiple seconds to parse it.
Btw, the UI component is called "Remote - Explorer".
Then I uninstalled the "Remote - Tunnels" extension. It cut down the 4 seconds to less than 1.
In fact, I could use my original config file and it still takes below 1s to load.
I am not using Tunnels so this is acceptable to me.
Activity
ian-h-chamberlain commentedon Apr 28, 2020
I noticed the same issue, it renders the SSH targets tab pretty much unusable in my case, unfortunately I cannot upload a profile for the same reason. In my case I have a 33-line config with ~10 hosts which
Includes another 93K line file with ~12K hosts in it.One thing I noticed however was that downgrading to version 0.49.0 of the extension allows me to actually use the SSH hosts tab again, but I can reliably reproduce with newer version of the extension
Remote - SSHextension and no other extensions enabled.RamyElkest commentedon Nov 2, 2020
Same issue here, almost the same amount ~7k hosts and the extension consistently fails to start (unresponsive).
As a workaround we extracted a subset of that hosts into a separate config which we set with
"remote.SSH.configFile".roblourens commentedon Nov 6, 2020
Interesting, we probably try to parse it too many times
hmc-cs-mdrissi commentedon Mar 16, 2024
This is still an issue and one I just hit. The extension is entirely unresponsive for any simple command. I have ~150k line long sshconfig (large number of company machines) that normal ssh command works fine, but this extension struggles with.
LunarLanding commentedon Mar 21, 2025
By filtering down the config to 4 hosts, I hoped I would fix this drag.
However, the extension still takes multiple seconds to parse it.
Btw, the UI component is called "Remote - Explorer".
Then I uninstalled the "Remote - Tunnels" extension. It cut down the 4 seconds to less than 1.
In fact, I could use my original config file and it still takes below 1s to load.
I am not using Tunnels so this is acceptable to me.