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…

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…

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.

Whoa, cool optimization by the Go compiler. If you do: b := make([]byte, 0, 40) // Bunch of stuff that appends 10-40 bytes to b) return string(b) How much memory will that function allocate on the heap?

self-aware Golang profile dumper. Contribute to mosn/holmes development by creating an account on GitHub.

#golang #performance folks, here are are my notes on "Goroutine Profiling in Go". It's probably the most comprehensive "docs" you'll find for this, at least I'm not aware of anything similar 🙃. Looking forward to feedback / questions / etc.! https://t.co/YqzARAzuKl

Here's a short list of the changes to look forward to for #golang 1.17, to start landing once the merge window opens in a few weeks.

Don't get confused with 1.16, releasing next month. 1.17 will come out in seven months.

Each change with a link, so you…

If @mdempsky finishes this (very likely) and Go 1.17 ships August 29th (might!) then it'll be exactly 10 years since I filed that wishlist compiler issue. 😂🎉🎂 https://t.co/sgIhhUV8WF

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...

Turns out you can reduce the memory usage of a #golang by ~1.4MiB (on 64bit) by simply calling this at the beginning of your main: runtime.MemProfileRate = 0

Good thread with retrospection of #golang runtime. Worth reading! https://t.co/ahMugm6wXy

📣 Releasing my #golang block profiler notes, covering: - What does the block profiler do? - How can you use it? - How does it work? - What's the overhead? - How accurate is it? It also comes with benchmarks, simulations and pretty graphs 🎉. Please RT htt…

I have just published a proposal to add fuzz testing support to Go, with the goal of making this an experimental feature for 1.17. @jayconrod and I have been working hard on this for a while, and are excited for this next big step! 🎉 https://t.co/reN4ZiHi2Z

Are you missing static variables ever since you switched from C(++) to #golang? Get them back with this one weird trick! https://t.co/GmUPBK41ln