Concurrency in Ruby

Presented at Burlington RubyConf 2014

Transcript

1. Concurrency in Ruby How to consume lots of data @dougalcorn
2. Concurrency in Ruby How to consume lots of data @dougalcorn ^ I consumed
3. Market Analytics in EVE with Ruby
4. Player
   Driven Economy
8. 1,250 * (14.02 - 13.00) = 1,275 ISK
10. EVE Market Data Relay Distributed price reporting via ZeroMQ
11. Big Thanks to Jim!
12. Big Thanks to Rob Pike!
13. Concurrency? •Events •Processes •IPC •Threads •Mutexes •Oh, my!
14. Concurrency is Good Design it’s not just about parallelism
15. Parallelism
16. A Naive Implementation
17. A Naive Implementation
18. A Naive Implementation
19. Celluloid Actor-based concurrent objects for Ruby “Each actor is a concurrent object running in its own thread, and every method invocation is wrapped in a fiber that can be suspended whenever it calls out to other actors, and resumed when the response is available.”
20. A Naive Async Implementation
21. Threads and Fibers
22. you probably don’t need it all Know your data
23. you probably don’t need it all Know your data
24. Big Ball of JSON Mud
25. Big Ball of JSON Mud
26. Messaging Flow
28. Command Pattern
29. Pipe Command Listener
30. ActiveRecord is Thread Safe Just use AR calls as normal Eventually, when you're done with the connection(s) and wish it to be returned to the pool, you call ActiveRecord::Base.clear_active_connections!
31. ActiveRecord is Thread Safe Manually check out a connection You are responsible for returning this connection to the pool.
32. ActiveRecord is Thread Safe Use .with_connection block syntax
33. Nobody understands the GIL with thanks to Jesse Storimer and Ilya Gigorik
34. Vague Plans for Ruby GIL
35. Performance
36. Performance
37. Conclusions
38. Conclusions • Concurrency is not parallelism
39. Conclusions • Concurrency is not parallelism • Learning concurrency patterns from Go was a big help
40. Conclusions • Concurrency is not parallelism • Learning concurrency patterns from Go was a big help • Celluloid gives us a good tool to model concurrency with OO design
41. Conclusions • Concurrency is not parallelism • Learning concurrency patterns from Go was a big help • Celluloid gives us a good tool to model concurrency with OO design • JRuby can give us true parallelism
42. Conclusions • Concurrency is not parallelism • Learning concurrency patterns from Go was a big help • Celluloid gives us a good tool to model concurrency with OO design • JRuby can give us true parallelism • “It all depends”
43. Conclusions • Concurrency is not parallelism • Learning concurrency patterns from Go was a big help • Celluloid gives us a good tool to model concurrency with OO design • JRuby can give us true parallelism • “It all depends” • Don’t use node