๐Ÿ‡บ๐Ÿ‡ฆ Go performance channel
1.53K subscribers
37 photos
375 links
Go performance, runtime, concurrency.

Talks, blogposts and open source projects for gophers.

Not affiliated with Go team.

https://go-perf.dev

(mail: hello@go-perf.dev / @olegkovalov)
Download Telegram
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/
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/
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
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
Thank you โค๏ธ