My builds have been very slow recently and I want to know why is `go build` so slow for me. Is it due to reading disks or something else?
What is the recommended way of profiling/debugging `go build`? I know that the `-x` flag prints detailed information of `go build` but it doesn't tell where is time spent. I am familiar with profiling ordinary Go programs with pprof, but how can I apply it to `go build`. An extensive search returned very few information as it hard to come up with a query for profiling `go build`, not profiling ordinary Go programs nor info about the `build` command itself. Thanks -- 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/e8ebf97b-1294-427e-878a-a359f673794cn%40googlegroups.com.
