Go-ing Further
summary
A small pipeline reads a file of ~50 common passwords (demo trimmed to 20) and uses the bcrypt-like generateFromPassword call to hash each. Early code deadlocks when the main goroutine both writes and reads a channel; moving the producer to another go routines and adding a WaitGroup fixes it. Replacing the single processor with 10 worker goroutines cuts runtime from ~7s to ~4s (and under 1s locally), showing practical scaling and closure/close pitfalls.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:21Go routines and concurrency model
- 9:14Problem setup and first attempt
- 18:35Debugging the deadlock issue
- 26:53Fixing with WaitGroup
- 32:48Scaling with multiple processors
- 37:36Splitting read and process steps
- 46:17Refactoring into functions
- 51:42Key takeaways and summary
related talks
22mOne Billion Row Challenge in Golang
34mGo concurrency in the real world
18mApplied concurrency in Go
01h 27mFlash Talks
24mMastering Concurrency in Go: From Patterns to Production
35mGo’s Trace Tooling and Concurrency
15mI came for the easy concurrency I stayed for the easy composition
06mHow We Achieved 100x Scale