gopls consumes permanent high CPU usage

[Klaus-Tockloth]

What version of Go, VS Code & VS Code Go extension are you using?

• go version go1.15.6 darwin/amd64
• golang.org/x/tools/gopls v0.6.0
• Visual Studio Code Version: 1.52.1
• Go for Visual Studio Code v0.19.1

Share the Go related settings you have added/edited

Describe the bug

gopls consumes after VS-Code start permanent high CPU usage (and does a lot of internet communication). VS-Code nearly unusable.

gopls (server) log attached.

gopls-server.log

[hyangah]

VSCode was opened from the GOPATH/src directory.
@stamblerre What is the current best practice in this case?

@Klaus-Tockloth Are all the packages under the GOPATH related? Is it possible to open only repo directories you intend to actively work on?

[Klaus-Tockloth]

Is it possible to open only repo directories you intend to actively work on?

The problem is gone, if I reduce my workspace.

Large Workspace with 'gopls' CPU consuming problem:

Small Workspace without 'gopls' CPU consuming problem (workspace reduce to folder 'klaus'):

Looks like a workaround ... thanks for pointing to this.

[stamblerre]

This case is specifically mentioned here: golang/go#36899. I know this issue is not very discoverable, but its contents will eventually be merged into our documentation. Opening your entire GOPATH/src is not actively supported, but you can use our new directoryFilters to exclude certain directories from analysis by gopls.

[hyangah]

@Klaus-Tockloth Great to hear that narrowing down the workspace scope made improvement. In general, Go is moving toward modules mode instead of GOPATH mode (eventually, GOPATH will be deprecated), I think it's time to consider the new module-based workflow.

@stamblerre thanks for the pointer. I updated #934 to include the workspace setup in the documentation. Let me close this issue and let's follow up in the documentation improvement work.