[mattetti]

The faster compilation time & speed up is quite real in our real life prod application.

From Go 1.6 to 1.7: Test suite (CI), from 3:34 to 1:48 Docker image building, from 3:05 to 1:50

https://twitter.com/mattetti/status/763913903600349184

[rmcpherson]

On our code base, we're seeing >2x build speed increases vs. go 1.6! Compiling the entire go monorepo, including vendored dependencies, dropped from 73 seconds to 29 on 4 CPUs when moving from 1.6.3->1.7rc6. Huge improvements to CI times, when amortized across go build, go test, docker builds etc.

[tbrock]

That's a ridiculous speed improvement. Holy shit.

[travjones]

Wow. That's impressive. Thanks for the example numbers, Matt!

[mattetti]

Thanks to the Go team, getting such an improvement without having to do anything is awesome. And I can't believe there is more coming in 1.8

[namelezz]

Following the twitter link and got this: "Something is technically wrong. Thanks for noticing—we're going to fix it up and have things back to normal soon."

[mintplant]

I've noticed this too on random pages. Seems Twitter is having issues today.

[travjones]

The link works for me. :)

[0xmohit]

From Go 1.5.4 to 1.7, I can see that the compilation time has improved. Didn't measure it, though.

However, the binary size didn't change appreciably. From 11129144 bytes, it reduced by 0.00179708340551618345%.

[jadbox]

How large-ish is your codebase?

[donatj]

That's what I was wondering. Our largest Go application takes maybe 5 seconds to compile clean. We largely use Go as a number of Microservices though.

[mattetti]

167912 LOC