To add a bit more information to this topic: I also have Vim + ale + gopls setup and I tried the same file with Vim + gopls auto complete and it was much faster in Vim. Based on my rough timing, I got the correct auto complete responses from gopls in Vim in about 1.5 seconds vs about 4-5 seconds in VSCode. I am using VSCode 1.46.1 on Linux. Could this in some way be a VSCode issue instead of gopls?
On Friday, July 3, 2020 at 3:43:53 PM UTC-4, Luke Mauldin wrote: > > I have a Go project that is relatively small in terms of number of files > (less than 30) but some Go files have auto-generated code that makes them > relatively large - some between 3-4 MB. I counted the SLOC using > https://github.com/hhatto/gocloc and it reports about 61K lines of code > and 40K lines of comments. When I am using `gopls` in my project on a > pretty high-end workstation (Intel Xeon W-2135, 32 GB RAM, SSD hard drive), > it is taking 4-5 seconds to give autocomplete suggestions in VSCode. Do > you have any recommendations of ways to improve the auto complete time? > Of note, one of the subdirectories of the project is a package that uses > CGO and it is wrapping about 440 C method calls. If it would help, I can > move that subdirectory into its own package entirely and reference it via > go.mod? > > Please let me know if you have any suggestions or if I should post this in > the `gopls` Github project. > > Luke > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/16f60edd-a9b4-499f-8202-53c0edf17903o%40googlegroups.com.
