About time.Sleep and how it's implemented under the hood, sure, it's about #golang runtime

https://xwu64.github.io/2019/02/27/Understanding-Golang-sleep-function/

#golang low-level calling convention on x86-64 (July 2018) by twitter.com/kena42

https://science.raphael.poss.name/go-calling-convention-x86-64.html

Memory profiling and load testing with Vegeta by twitter.com/mark_a_phelps

https://www.markphelps.me/2019/11/profiling-to-reduce-memory-allocations/

Analyzing #golang Executables by twitter.com/jebdec


Well, it's not about performance, but a very good post about executable internals.

https://pnfsoftware.com/blog/analyzing-golang-executables/

Sometimes you want to check new features from #golang master branch (also called tip).

There is no need to do it manually, just use gotip tool which does this perfectly

https://godoc.org/golang.org/dl/gotip

Have you read A Million WebSockets story with #golang ? It's from 2017 but twitter.com/gobwas has shared a lot of insights and low-level things. Repo: https://github.com/gobwas/ws

https://medium.freecodecamp.org/million-websockets-and-go-cc58418460bb

See a new article by @GopherAcademy about #golang pointers and how to use them properly (also checkptr command)

Quick example for check pointer:
gotip run -gcflags=all=-d=checkptr main.go)

https://blog.gopheracademy.com/advent-2019/safe-use-of-unsafe-pointer/

How syscalls are handled by #golang runtime https://utcc.utoronto.ca/~cks/space/blog/programming/GoSchedulerAndSyscalls

And again about memory, but now from a transistor level to #golang GC https://blog.learngoprogramming.com/a-visual-guide-to-golang-memory-allocator-from-ground-up-e132258453ed

An experiment in rewriting sync primitives via #golang channels. Not a thing for production use, but a good practice, thanks twitter.com/empijei

https://blogtitle.github.io/go-advanced-concurrency-patterns-part-3-channels/

User defined traces for go tool trace util and an example how to use it #golang

https://medium.com/@felipedutratine/user-defined-runtime-trace-3280db7fe209

Post by twitter.com/commaok about interning strings in #golang https://commaok.xyz/post/intern-strings/

Sneaky race conditions and granular locks #golang and #rust by twitter.com/empijei

https://blogtitle.github.io/sneaky-race-conditions-and-granular-locks/

An interesting optimisation in #golang math/rand package by twitter.com/cafxx. Devirtualizing (avoiding interface calls) often improves code performance, but don't overuse it, please (it makes sense for hot code path).

https://go-review.googlesource.com/c/go/+/191538/

Famous story from Uber: How Uber Halved Our Metrics Ingestion Latency by (Briefly) Forking the #golang Compiler

https://eng.uber.com/optimizing-m3/

Despite the fact that #golang finalizers are dangerous (if you're not paying attention) they really might improve performance of your application and give additional benefits.

See: Autopool Speeding Up gRPC With Finalizers
https://gophersre.com/2019/12/31/autopool/

Repo: https://github.com/johnsiilver/golib/tree/master/development/autopool/blend

Scheduling and GC article also have part 2,3, don't forget to read them too 😉 #golang

RT:
Here are the top blog posts from 2019:

1. Iterating Over Slices In Go
https://www.ardanlabs.com/blog/2013/09/iterating-over-slices-in-go.html
2. Scheduling In Go: Part I - OS Scheduler
https://www.ardanlabs.com/blog/2018/08/scheduling-in-go-part1.html
3. Garbage Collection In Go: Part I - Semantics
https://www.ardanlabs.com/blog/2018/12/garbage-collection-in-go-part1-semantics.html

(I'm sorry for a little break, but...)

If you're going to work with UDP sockets in #golang be aware of this article (2018). Bunch of details, explanations and examples. Thank you twitter.com/cirowrc

https://ops.tips/blog/udp-client-and-server-in-go/#receiving-from-a-udp-connection-in-a-server

How we optimized our DNS server using #golang tools

https://medium.com/@arash.cordi/how-we-optimized-our-dns-server-using-go-tools-d753e1a5e709

(from @count0_digest)

From today series of #golang proposals regarding changes in runtime, compiler and all this strange stuff will be posted here.

The first one in the series: Create an undefined internal calling convention (by Austin Clements) https://github.com/golang/proposal/blob/master/design/27539-internal-abi.md