Why JRuby?
summary
Explains why J Ruby beats MRI for many real deployments by showing concrete wins not slogans: invoke dynamic optimizations on Java 7 that let the JVM inline dynamic Ruby calls, G1 and concurrent garbage collectors that drop pause times to ~0.1s versus long MRI stops, and Torquebox bundling messaging caching scheduled jobs into one JVM server. Demos include JavaFX and 3D libraries called from Ruby, Minecraft plugin examples, and multi‑threaded benchmarks that saturate cores in one process.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:10Ruby on JVM
- 1:47caveats
- 3:00JRuby 1.7
- 3:42Getting Started
- 6:38JRuby Structure
- 7:30JRuby Team Doesn't Have to Work On
- 8:23Systems
- 10:48Servers
- 11:41Ruby App
- 13:20Ruby-friendly Config
- 13:50Messaging
- 14:25Libraries
- 15:42JavaFX
- 19:22Threepence
- 22:20GC Matters
- 22:50JVM GC
- 28:26Real Parallellism
- 30:20Nonlinear?
- 30:41Profiling
- 31:27Monitoring
- 35:00Performance
- 40:54Your Turn
