x/build: collect stats, logs

[bradfitz]

The coordinator should record per-build logs, and also keep statistics about timing information in BigQuery or something.

Then we can graph build times, test times, individual test times, machine bootup times, etc, all over time.

Related: #12668 (shootout tests talke 30 mins on arm)

[alexbrainman]

I wanted something similar many times. We have many people changing things now. But no one is looking after performance. Are things getting better over time? Worse? It is impossible to tell.

Alex

[davecheney]

I have been keeping an eye on performance for the changes that are going
into the compiler. Fwiw, we clawed back from 91mins to 88mins (on arm) over
the last few weeks. Of course, we lost 30 mins because something has gone
bonkers with the shootout tests.

I agree, it would be great to have something like Dmitry's performance
dashboard back again.

On Fri, 18 Sep 2015 09:27 Alex Brainman notifications@github.com wrote:

I wanted something similar many times. We have many people changing things
now. But no one is looking after performance. Are things getting better
over time? Worse? It is impossible to tell.

Alex

—
Reply to this email directly or view it on GitHub
#12669 (comment).

[bradfitz]

Btw, this bug is not about the performance dashboard so much as it is about monitoring the health of the build system itself.

[gopherbot]

CL https://golang.org/cl/21570 mentions this issue.

[gopherbot]

CL https://golang.org/cl/21640 mentions this issue.

[gopherbot]

CL https://golang.org/cl/21968 mentions this issue.

[gopherbot]

CL https://golang.org/cl/22701 mentions this issue.

[gopherbot]

CL https://golang.org/cl/22705 mentions this issue.