🇺🇦 Go performance channel
https://twitter.com/calebspare/status/1546928290123812864
Twitter
New #Go memory model seems to be like Java: no undefined behavior due to data races, only race conditions (all variables are atomic-ish). This inhibits lots of compiler optimizations C/C++ compilers typically do.
But races on strings/maps still lead to arbitrary…
But races on strings/maps still lead to arbitrary…
Nice #golang proposal by twitter.com/mbmcloughlin is accepted 🎉:
testing: add Elapsed() method to testing.B
https://github.com/golang/go/issues/43620
testing: add Elapsed() method to testing.B
https://github.com/golang/go/issues/43620
X (formerly Twitter)
Michael McLoughlin (@mbmcloughlin) on X
Mathematical Software Engineer.
Mastodon @[email protected]
Bluesky @mmcloughlin.com
Mastodon @[email protected]
Bluesky @mmcloughlin.com
🇺🇦 Go performance channel
Nice #golang proposal by twitter.com/mbmcloughlin is accepted 🎉: testing: add Elapsed() method to testing.B https://github.com/golang/go/issues/43620
One more step to the better #golang benchmarks (now by twitter.com/mknyswe, also accepted 😉):
testing: report GC/op when b.ReportAllocs is called
https://github.com/golang/go/issues/52466
testing: report GC/op when b.ReportAllocs is called
https://github.com/golang/go/issues/52466
X (formerly Twitter)
mknyszek (@mknyswe) on X
works on @golang runtime | he/him
> We’re all agreed that we want something platform-independent and vector-length agnostic. ARM is especially interested in it being vector-length agnostic because of new SVE instructions.
❤️🔥
Src: #golang compiler and runtime meeting notes (golang/go issue 43930)
❤️🔥
Src: #golang compiler and runtime meeting notes (golang/go issue 43930)
🇺🇦 Go performance channel
> We’re all agreed that we want something platform-independent and vector-length agnostic. ARM is especially interested in it being vector-length agnostic because of new SVE instructions. ❤️🔥 Src: #golang compiler and runtime meeting notes (golang/go issue…
To be honest @Arm Memory Tagging Extension is also a hot thing but more about safety rather than performance.
🇺🇦 Go performance channel
To be honest @Arm Memory Tagging Extension is also a hot thing but more about safety rather than performance.
Twitter
@go_perf @Arm There may be some applications for GCs. E.g. marking pointers to objects w/o pointers (don't need scanning) or encoding object size right in the pointer (for some common small sizes at least).
Things are getting interesting (#golang PGO for Go 1.20)
GOMEMLIMIT is a game changer for high-memory applications by @weaviate
https://weaviate.io/blog/2022/08/GOMEMLIMIT-a-Game-Changer-for-High-Memory-Applications.html #golang
https://weaviate.io/blog/2022/08/GOMEMLIMIT-a-Game-Changer-for-High-Memory-Applications.html #golang
weaviate.io
GOMEMLIMIT is a game changer for high-memory applications | Weaviate
Go 1.19 introduced GOMEMLIMIT, which completely changes how you can manage memory limits in Go. Learn how it helps Weaviate be more reliable.
#golang string<->bytes dark magic landed again.
https://github.com/golang/go/commit/cf26fbb1f6d9644f447342f42d2dddcbe9ceda61 by _joetsai
https://github.com/golang/go/commit/cf26fbb1f6d9644f447342f42d2dddcbe9ceda61 by _joetsai