On Tue, Dec 5, 2017 at 10:51 AM, Clayton Coleman <[email protected]> wrote:
> Openshift and Kubernetes are massive go projects - over 3 million lines of > code (last I checked). Initial compile can take a few minutes for these > tools. Things to check: > > 1. Go 1.9 uses less memory when compiling > 2. Be sure you are reusing your go compiled artifacts dir between multiple > tools (sometimes that is GOPATH/pkg, but openshift explicitly only compiles > temp packages into _output/local/pkgdir for reasons) > So if I make clean all and then run my guru command, won't that be reusing compiled artifacts? Is there some config that controls this? I don't think I've customized anything. It does seem to speed up a little bit after the first run but then it's still pretty slow. > 3. Get faster laptop :) > > On Dec 5, 2017, at 9:44 AM, Luke Meyer <[email protected]> wrote: > > In the context of the vim-go plugin. However behavior seems much the same > if I run the same command at the command line (I pulled it out of ps -ef). > > On Tue, Dec 5, 2017 at 10:40 AM, Sebastian Jug <[email protected]> wrote: > >> Are you using guru in some sort of editor/IDE or just standalone? >> >> On Dec 5, 2017 9:40 AM, "Luke Meyer" <[email protected]> wrote: >> >>> >>> >>> On Tue, Dec 5, 2017 at 9:36 AM, Sebastian Jug <[email protected]> wrote: >>> >>>> Sounds like you have got auto compile still on? >>>> >>>> >>> What does this mean in the context of go guru? Is there an env var to >>> set, an option to add, a config file to change to control this behavior? >>> >>> >> > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
