← Dashboard
jespinog

JesΓΊs Espino βœ“

2.1K followers
5 tweets
Communities: Golang Insiders
# Tweet Community Topic Views β–Ό Ratio Engagement Posted
1
[image] New article: Go's Memory Allocator πŸš€ How Go manages heap memory for thousands of goroutines. 64MB arenas β†’ 8KB pages β†’ spans β†’ fixed-size slots. A three-level cache where the fast path is completely lock-free. πŸ‘‰ #golang #go #runtime #programming
Golang Insiders β€” 28.4K 18.8x 222 Feb 23
2
[image] New article: Inside Go's Runtime Scheduler πŸš€ How Go runs millions of goroutines on a few OS threads. The GMP model, work stealing, spinning threads, and context switches that take only 50-100 nanoseconds (10-40x faster than OS threads). πŸ‘‰ #golang
Golang Insiders β€” 23.8K 14.7x 191 Mar 9
3
[image] "The select Statement" is a lighter entry in the Go runtime series, but it's one of my favorites because it shows something I think is genuinely beautiful: how the compiler and the runtime collaborate. A `select` looks like a switch, but underneath it's really two features: The
Golang Insiders β€” 19.0K 9.4x 84 May 18
4
[image] I just published "Stacktraces", the next piece in my "Understanding the Go Runtime" series, and it answers a question we all take for granted: how does the runtime know the entire call chain when your program panics? The trace is built in two phases, and once you see them the
Golang Insiders β€” 6.8K 3.2x 62 Jun 1
5
[image] New article: The Go System Monitor How sysmon, a thread with no P, keeps the runtime fair. It preempts goroutines, retakes Ps from syscalls, forces GC every 2 minutes, and ensure network poller keeps ticking. The Go's watchdog #golang #go #runtime
Golang Insiders β€” 4.7K 2.7x 55 Apr 6
6
[image] New article: Inside Go's Garbage Collector 🧹 How Go reclaims memory without stopping your program. Tri-color marking, write barriers, span-based batching, SIMD-accelerated scanning, and drafting goroutines into helping GC when they allocate too fast. πŸ‘‰
Golang Insiders β€” 2.9K 1.7x 64 Mar 23