x/tools/gopls: >45s for first completion of unimported package #36222
Comments
@gopherbot please remove label Documentation |
I'm going to hijack this for a braindump of performance problems with unimported completions.
|
Notes to self as of https://golang.org/cl/212634:
|
Submitted a bunch of stuff. Most everything from the above is done. Remaining:
|
Since I keep getting distracted, one more update: https://golang.org/cl/212022 is the last thing I intend to do here. Other than that we should be in good shape. |
This should be fixed, or at least fixed enough to be on by default. |
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Open up a new module
Then type in:
And at
|
trigger a completion request.What did you expect to see?
Completion request return a little bit faster.
What did you see instead?
The response arrives after ~47 seconds. See https://gist.github.com/leitzler/29eca825af07416bae63c1c304527994#file-gopls-log-L429
As per discussion on Slack with @heschik it looks like it is due to package name loading.
Rerun with verboseOutput:
Mod cache size:
The text was updated successfully, but these errors were encountered: