At the #golang North East meetup today
twitter.com/mvdan_
presented "Measuring Go's init performance cost". Here are graphs of the top 20 costs (bytes alloc and time) obtained by running:
GODEBUG=inittrace=1 go env GOARCH'
(this will be in Go 1.16, and available at tip now)
twitter.com/mvdan_
presented "Measuring Go's init performance cost". Here are graphs of the top 20 costs (bytes alloc and time) obtained by running:
GODEBUG=inittrace=1 go env GOARCH'
(this will be in Go 1.16, and available at tip now)
🇺🇦 Go performance channel
At the #golang North East meetup today twitter.com/mvdan_ presented "Measuring Go's init performance cost". Here are graphs of the top 20 costs (bytes alloc and time) obtained by running: GODEBUG=inittrace=1 go env GOARCH' (this will be in Go 1.16, and…
See also https://www.tgoop.com/go_perf/45
Telegram
Go performance channel
What a beautiful thing! In #golang 1.16 you can track how much time is spent in init() funcs! what a nice thing to have!
https://github.com/golang/go/issues/41378
https://github.com/golang/go/issues/41378
A story how twitter.com/srcgraph made their #golang backend faster
https://about.sourcegraph.com/blog/optimizing-a-code-intel-backend/
https://about.sourcegraph.com/blog/optimizing-a-code-intel-backend/
Hacked string interning profiler for #golang:
https://go-review.googlesource.com/c/go/+/277376
Allows to understand where to use interning & exact savings for heap size/garbage rate. May be useful for larger projects.
Yay or nay?
https://twitter.com/dvyukov/status/1337847667125313538
https://go-review.googlesource.com/c/go/+/277376
Allows to understand where to use interning & exact savings for heap size/garbage rate. May be useful for larger projects.
Yay or nay?
https://twitter.com/dvyukov/status/1337847667125313538
Twitter
Dmitry Vyukov
Hacked string interning profiler for #golang: https://t.co/EB2uJwzvtx Allows to understand where to use interning & exact savings for heap size/garbage rate. May be useful for larger projects. Yay or nay?
Even if it's a WIP, still worth to mention and follow 👀
Anyway string interning in #golang is a long-running topic and it's always interesting to see what is going on :)
Anyway string interning in #golang is a long-running topic and it's always interesting to see what is going on :)
Links from patch/commit:
https://github.com/golang/go/issues/5160
https://github.com/golang/go/issues/32593
https://github.com/golang/go/issues/32779
https://commaok.xyz/post/intern-strings/
https://artem.krylysov.com/blog/2018/12/12/string-interning-in-go/
https://godoc.org/github.com/josharian/intern
https://godoc.org/github.com/chriso/go-intern
https://github.com/golang/go/issues/5160
https://github.com/golang/go/issues/32593
https://github.com/golang/go/issues/32779
https://commaok.xyz/post/intern-strings/
https://artem.krylysov.com/blog/2018/12/12/string-interning-in-go/
https://godoc.org/github.com/josharian/intern
https://godoc.org/github.com/chriso/go-intern
Austin Clements (from #golang team) @GopherCon about runtime changes in 1.14 and what is this loop preemption beast?
https://www.youtube.com/watch?v=1I1WmeSjRSw
PS: Austin's talk is an amazing gift, right before Christmas :D
https://www.youtube.com/watch?v=1I1WmeSjRSw
PS: Austin's talk is an amazing gift, right before Christmas :D
YouTube
GopherCon 2020: Pardon the Interruption: Loop Preemption in Go 1.14 - Austin Clements
Go 1.14 significantly changed how goroutines are preempted for scheduling and garbage collection. Since Go 1.2, the Go runtime has preempted goroutines only at function calls. Most of the time, this let Go developers ignore preemption and focus on writing…
Now let's jump to the allocator changes and how to return memory back to OS by Michael Knyszek (from #golang team) at @GopherCon
Did you get this tree fix (ts@18:50) ? Heavy one. Bitmap tree is an another gem from runtime pkg
https://www.youtube.com/watch?v=S_1YfTfuWmo
PS: Christmas gifts 2.0 :D
Did you get this tree fix (ts@18:50) ? Heavy one. Bitmap tree is an another gem from runtime pkg
https://www.youtube.com/watch?v=S_1YfTfuWmo
PS: Christmas gifts 2.0 :D
YouTube
GopherCon 2020: Evolving the Go Memory Manager's RAM and CPU Efficiency - Michael Knyszek
This talk will discuss recent changes to the Go memory manager, which improved both the runtime’s responsiveness in giving up unneeded memory and the scalability of the memory allocator. In this presentation, Michael peeks under the hood of the runtime, examines…
You know what? One more great talk from @GopherCon by Agniva De Sarker about Bound check elimination in #golang
Look at the examples, they're very explanatory!
https://www.youtube.com/watch?v=5toTS6kSWHA
Look at the examples, they're very explanatory!
https://www.youtube.com/watch?v=5toTS6kSWHA
YouTube
GopherCon 2020: Common Patterns for Bounds Check Elimination - Agniva De Sarker
Bounds checks are a necessary evil. If you don’t have them, you lose memory safety. If you have them, you hurt performance. Is it possible to have the best of both worlds? Why, yes! Watch this talk to learn more.
Back to string interning in #golang by
twitter.com/mdlayher
https://mdlayher.com/blog/unsafe-string-interning-in-go/
twitter.com/mdlayher
https://mdlayher.com/blog/unsafe-string-interning-in-go/
Allocations, size classes in #golang by twitter.com/davecheney
https://dave.cheney.net/2021/01/05/a-few-bytes-here-a-few-there-pretty-soon-youre-talking-real-memory
https://dave.cheney.net/2021/01/05/a-few-bytes-here-a-few-there-pretty-soon-youre-talking-real-memory
Neat #golang trick how to pack multiple slice allocations into one (or less than in a naive way), thanks to twitter.com/tvii for showing this!
https://vladimir.varank.in/notes/2019/09/go-http-headers/
(slices are amazing)
https://vladimir.varank.in/notes/2019/09/go-http-headers/
(slices are amazing)
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...