Threading versus Evented
summary
Argues that for most web apps threads are the practical win: process-per-request costs ~50–150MB each while thread stacks are tiny, so wrap code in threads and move short, nonblocking IO to the front. Recommends JRuby with Trinidad or Rubinius 2.0 for native-thread runtimes, default JRuby thread limit ~200, and fronting with use nginx in front (evented loop for static/cache and proxying) while keeping worker code short and avoid Thread.new littered through app.
AI-written summary · about
chapters (7)
- 0:00Start
- 16:05GIL = Global Interpreter Lock
- 24:22I'm scared of threads
- 25:54What is evented?
- 28:00Rule: Evented code should not
- 29:21How do I use both and write complex apps?
- 34:21Ruby web server built for concurrency
