-
Notifications
You must be signed in to change notification settings - Fork 17.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/gopls: slow performance #43259
Comments
Can you please share your |
Here's a pretty clean trace from the moment I started typing (same as in the video) until the gopls activity stopped. |
There are a number of cancelled requests like these:
|
@zhaytee: Above, you mention that your workspace folder is Also, it looks like you've shared an incomplete log. Can you please include a log that starts from the |
Apologies, I haven't had time to update this issue properly. However, I did want to mention that I recently upgraded the version of Go on my dev box from 1.14.9 to 1.15.6, and things seem a LOT faster. I don't know if there's a good reason for that, or if it's just a coincidence. |
Glad things are working better now. I'll go ahead and close this since the issue's resolved, but feel free to reopen if you run into it again. |
What version of Go, VS Code & VS Code Go extension are you using?
go version: go1.14.9 linux/amd64
gopls version: golang.org/x/tools/gopls v0.6.1
vscode version: 1.52.1 (commit ea3859d4ba2f3e577a159bc91e3074c5d85c0523)
vscode-go version: 0.19.1
Share the Go related settings you have added/edited
Describe the bug
VSCode is running on macOS, vscode-go is running on linux/amd64 (I'm using the remote-ssh extension).
Apologies if this is a duplicate, but I couldn't find anything quite similar in the issues log.
Performance is very slow when gopls is performing autocomplete. It takes many seconds (between 3 and 5) to pop up the autocomplete dialog, which is just way too long when I'm trying to move fast.
Please see the linked video for a quick demo: https://www.youtube.com/watch?v=H2aCyG7e_hY
Notice the gopls debugging output. I don't see any one response type standing out as being the slowest; all of the relevant ones seem to be really slow: codeAction, foldingRange, documentLink, codeLens, documentSymbol, completion, etc.
Any help to speed this up would be greatly appreciated! Thank you.
The text was updated successfully, but these errors were encountered: