-
Notifications
You must be signed in to change notification settings - Fork 89
Take 3s to go to definition for symbol of internal package #323
Comments
Can you include your go config for vscode? Any diagnostic output to help diagnose? Is this in OSS, so I can try reproduce? |
Here is my go config "go.docsTool": "gogetdoc",
"go.languageServerExperimentalFeatures": {
"autoComplete": true,
},
"go.languageServerFlags": [
"-diagnostics",
],
"go.useLanguageServer": true, go-langserver output:
If sub package (e.g.: Sorry, It's not OSS. |
If you remove the |
It was running slow without it. tried to add it to see if there is some info, but no info. |
Thanks for the information. This should still be fast regardless. I'll check if we have regressed on which j2d engine we use with your flags (we have a slower one which is more correct, but by default we should be using a godef based j2d). |
Thanks for checking :) |
We haven't regressed here. I'm unsure how deep you want to get into this, but a pprof profile of what its doing to take that long would be amazing. https://github.com/sourcegraph/go-langserver#profiling |
Here we go. "go.languageServerExperimentalFeatures": {
// "autoComplete": true,
},
"go.languageServerFlags": [
"-pprof",
"localhost:6060",
],
"go.useLanguageServer": true,
|
Ah, it's like this, try to jump to Definition of:
I guess if a package (excluding children package) is to big, it'll be slow because of i/o bottle neck. |
In vscode:
For symbol of internal package (the package that I'm coding), it takes 3s to jumps to the definition.
For symbol of external packages (packages that are in vendor) , it jumps nearly instantly.
macOS High Sierra 10.13.16
The text was updated successfully, but these errors were encountered: