If the answer is just "go guru is dog slow, use something else in that
case" then that seems like a useful thing to note in the README :) Along
with what people actually use in development. Seems like a number of tools
rely on guru but everyone complains about how slow it is on large projects.
So
On Tue, Dec 5, 2017 at 10:51 AM, Clayton Coleman
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
On Tue, Dec 5, 2017 at 10:43 AM, Luke Meyer 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
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
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 wrote:
> Are you using guru in some sort of editor/IDE or just standalone?
>
> On
-- Forwarded message --
From: Luke Meyer <lme...@redhat.com>
Date: Tue, Dec 5, 2017 at 10:39 AM
Subject: Re: [aos-devel] optimizing go guru
To: Sebastian Jug <se...@redhat.com>
Cc: dev <d...@lists-openshift-redhat-com.vserver.prod.ext.phx2.redhat.com>
On Tue