Hey #gophers ! #golang compiler and runtime meeting notes are public!
Subscribe and follow all the new and amazing things happening in Go ๐๐๐
https://github.com/golang/go/issues/43930
Subscribe and follow all the new and amazing things happening in Go ๐๐๐
https://github.com/golang/go/issues/43930
GitHub
Go compiler and runtime meeting notes ยท Issue #43930 ยท golang/go
Google's Go compiler and runtime team meets periodically (roughly weekly) to discuss ongoing development of the compiler and runtime. While not open to the public, there's been desire by th...
New #golang GC Pacer desing by twitter.com/mknyswe
https://go.googlesource.com/proposal/+/a216b56e743c5b6b300b3ef1673ee62684b5b63b/design/44167-gc-pacer-redesign.md
Still at proposal phase, but worth to read https://github.com/golang/go/issues/44167
https://go.googlesource.com/proposal/+/a216b56e743c5b6b300b3ef1673ee62684b5b63b/design/44167-gc-pacer-redesign.md
Still at proposal phase, but worth to read https://github.com/golang/go/issues/44167
Cool stuff: buffer pool in #golang based on databases.
Also a neat part: CLOCK Replacement algorithm (read as better LRU, LFU policy)(however better can be argued :)
Thank you twitter.com/brunocalza !
https://brunocalza.me/how-buffer-pool-works-an-implementation-in-go/
Also a neat part: CLOCK Replacement algorithm (read as better LRU, LFU policy)(however better can be argued :)
Thank you twitter.com/brunocalza !
https://brunocalza.me/how-buffer-pool-works-an-implementation-in-go/
Better IP addr in #golang by twitter.com/tailscale (and twitter.com/bradfitz)
The article isnโt about performance only, but the criteria for a new type are well described https://tailscale.com/blog/netaddr-new-ip-type-for-go/
The article isnโt about performance only, but the criteria for a new type are well described https://tailscale.com/blog/netaddr-new-ip-type-for-go/
Go compiler and runtime meeting notes (https://github.com/golang/go/issues/43930)
> We discussed how to address amd64 per-architecture optimizations. Haswell specific optimizations have shown large improvements in certain workloads, and it might be worth providing for these wins. Discussion will likely continue.
Also see:
cmd/compile: add GOAMD64 architecture variants (https://github.com/golang/go/issues/25489)
https://github.com/golang/go/issues/25489
> We discussed how to address amd64 per-architecture optimizations. Haswell specific optimizations have shown large improvements in certain workloads, and it might be worth providing for these wins. Discussion will likely continue.
Also see:
cmd/compile: add GOAMD64 architecture variants (https://github.com/golang/go/issues/25489)
https://github.com/golang/go/issues/25489
GitHub
Go compiler and runtime meeting notes ยท Issue #43930 ยท golang/go
Google's Go compiler and runtime team meets periodically (roughly weekly) to discuss ongoing development of the compiler and runtime. While not open to the public, there's been desire by th...
Register-based calling convention for #golang functions is alive. Which is super great! Fingers crossed that it will land in Go 1.17 this ~August.
https://github.com/golang/go/issues/40724
https://github.com/golang/go/issues/40724
The Ryu algorithm for fast float64->decimal conversion.
Almost 5 years later it's merged, @dvyukov you should be happy, right? :D
Hope it will land in #golang 1.17 this August (or so) https://github.com/golang/go/issues/15672
Special thanks to @oudomphe CC: @ulfjack (Ryu author) and @calebspare
Almost 5 years later it's merged, @dvyukov you should be happy, right? :D
Hope it will land in #golang 1.17 this August (or so) https://github.com/golang/go/issues/15672
Special thanks to @oudomphe CC: @ulfjack (Ryu author) and @calebspare
GitHub
strconv: implement the Ryu algorithm to speed up float64->decimal conversion ยท Issue #15672 ยท golang/go
go version devel +15f2d0e Fri May 13 01:19:05 2016 +0000 linux/amd64 func BenchmarkAppendFloatLarge1(b *testing.B) { benchmarkAppendFloat(b, 622666234635.321e-320, 'e', -1, 64) } func Bench...
๐บ๐ฆ Go performance channel
Register-based calling convention for #golang functions is alive. Which is super great! Fingers crossed that it will land in Go 1.17 this ~August. https://github.com/golang/go/issues/40724
The results are looking phenomenal. On a set of application benchmarks we've been using, geomean improvement is 6%
Great! #golang
Great! #golang