๐Ÿ‡บ๐Ÿ‡ฆ Go performance channel
1.5K subscribers
39 photos
401 links
Go performance, runtime, concurrency.

Talks, blogposts and open source projects for gophers.

Not affiliated with Go team.

https://go-perf.dev

(mail: [email protected] / @olegkovalov)
Download Telegram
Allow more inlining of functions that construct closures #golang

> This will help significantly with the performance of the functions <...>, which have a somewhat complicated nesting of closures with a performance-critical fast path.

https://go-review.googlesource.com/c/go/+/482356
> We are using the Iguana compression already in Sneller Cloud for very fast and efficient log analysis. We are planning on releasing it as a standalone compression library for #golang in the near future.

https://sneller.io/blog/decompressing-at-over-10-gigabytes-per-second/
๐Ÿ‡บ๐Ÿ‡ฆ Go performance channel
Execution tracer overhaul by @mknyswe #golang issue: https://github.com/golang/go/issues/60773 & doc: https://go.googlesource.com/proposal/+/ac09a140c3d26f8bb62cbad8969c8b154f93ead6/design/60773-execution-tracer-overhaul.md
> Thanks to work in Go 1.21 cycle, the execution tracerโ€™s run-time overhead was reduced from about -10% throughput and +10% request latency in web services to about 1% in both for most applications.
๐Ÿ‡บ๐Ÿ‡ฆ Go performance channel
โ€œGo 1.21 Release Candidateโ€ by @elibendersky โ€” go.dev/blog/go1.21rc
> Go 1.21 improves build speed by up to 6%, largely thanks to building the compiler itself with PGO.
From https://github.com/golang/go/issues/43930

> SwissTable: Google3 may want to do some benchmarking on this. Maps are used heavily in google3. This may be of value to us.

There is a chance that next #golang releases will have a faster map implementation!

(Note: Google3 is Google's monorepo)
#golang linker optimisation in upcoming Go 1.21 https://go-review.googlesource.com/c/go/+/490915

(There is even more changes, see drop from Apr 24)