3 ms·
Great work, Go team! Standout points in my opinion: Overall performance improvements: >> "We observed a 5–35% speedup across our benchmarks." Decreased comp
by travjones 10y ago
Great work, Go team!
Standout points in my opinion:
Overall performance improvements:
>> "We observed a 5–35% speedup across our benchmarks."
Decreased compile times and binary size:
>> "While these changes across the compiler toolchain are mostly invisible, users have observed a significant speedup in compile time and a reduction in binary size by as much as 20–30%."
Vendoring dependencies by default:
>> "...and in Go 1.7... the "vendor" behavior is always enabled"
Context package added to std lib:
>> "To make use of contexts within the standard library and to encourage more extensive use, the package has been moved from the x/net repository to the standard library as the context package."
- mattetti 10y agoThe 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 https://twitter.com/mattetti/status/763913903600349184
- namelezz 10y agoFollowing 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."
- travjones 10y agoWow. That's impressive. Thanks for the example numbers, Matt!
- mattetti 10y agoThanks 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
- tbrock 10y agoThat's a ridiculous speed improvement. Holy shit.
- tychuz 10y ago1. Make compile times slower for every release. 2. Restore compile times to 1.3 or so levels. 3. Collect praise from g-sheep.
- _ph_ 10y agoYes, compile times have gotten worse in some releases, but there were good technical reasons for the trade-off, mainly the general quality improvements of the go environment. But the good news is, they are not resting but trying to gain back the lost speed - you do not observe this always in larger programs. Calling people happy about this "g-sheep" is unnecessary name-calling.
- rogerdpack 10y agoIt would be interesting to see some benchmarks from each version... :)
- jadbox 10y agoHow large-ish is your codebase?
- rmcpherson 10y agoOn 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.
- deleted 10y ago[deleted]
- 0xmohit 10y agoFrom 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%.