WSL remote: High CPU from watcher service

[bpasero]

I am seeing an increasing number of people complaining about high CPU in remote scenarios from the watcherService. My understanding is that we run with polling in those environments because the file system capabilities do not allow for proper file watching.

We should at least try to figure out a better default to reduce high CPU loads or maybe allow the user to configure this.

Extracted from #118613 (comment)

[alimbada]

@bpasero thanks for creating this. Just to add a bit more context, this has only become an issue since upgrading to 1.54.x. There were no problems prior to the upgrade.

[aeschli]

It's already configurable:

• remote.WSL.fileWatcher.polling (default true) to control whether polling is used or not
• remote.WSL.fileWatcher.pollingInterval: to change the default polling interval

But there has been many complaints of high CPU loads. So I'm going to change the default to false.

[aeschli]

duplicate of microsoft/vscode-remote-release#4637