Keegan Carruthers-Smith

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...

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

It would be fixed by #83, but it needs to be picked back up. I was having issues with how it behaved at end of file last time I tested...

@dbaeumer so the whole document range is ``` start: {line: 0, character: 0} end: {line: lastline, character: len(doc[lastline])} ``` ? what do you put if the file has more than...

Thanks for the report @chandradeepak as well as the profile. How does the resource usage compare to the reference finder without the language server? Our reference implementation is a modified...

The trace seems to point to most of the time spent reading files. Right now the implementation relies on the go typechecker. It shouldn't do more work than go does...

Sorry, I missed your reply. @chandradeepak if you still have this issue, how does the perf compare to just vscode-go without the langserver? You say you have 50 files, how...

Can you share your config? Have you enabled any optional features like code completion or diagnostics?

You are not opting into anything that should make go-langserver that slow. 1281 files should be fine. We run go-langserver on sourcegraph.com and don't use as much resources for large...

@Sp4rd4 for now just disable the language server. If your performance improves report back here.