Ruby 1.9 Fibers
16 likes6,108 views
The document discusses Ruby 1.9 fibers, emphasizing their role in cooperative multi-processing and event-driven programming. It compares processes, threads, and fibers, highlighting the lightweight nature of fibers and their ability to simplify asynchronous code, while also presenting examples of event-driven programming. The document concludes by noting the advantages of event-based architectures and the growing popularity of fibers in Ruby applications.
More Related Content
Ruby 1.9 Fibers
- 1. Ruby 1.9 Fibers Cooperative Multi-Processing and Elegant Event-Driven Programming Kevin Ball Co-Founder and CTO fashioningchange.com [email protected] http://twitter.com/kbal11
- 2. Outline • Multi-Processing Overview • Ruby Fibers • Event Driven Programming • Fibers + Events => Ruby FTW
- 3. Multi-Processing • Processes • Threads • Fibers • Events
- 4. Processes • Independent (no shared state) • Interact via message passing if at all • Preemptively scheduled • Fairly heavyweight
- 6. Why Processes? • OS managed
- 7. Why Processes? • OS managed • Task-level parallelism
- 8. Why Processes? • OS managed • Task-level parallelism • Great for embarrassingly parallel (IE web)
- 9. Threads • Shared Data • Fairly lightweight • Also Preemptively Scheduled
- 10. Why Threading?
- 11. Why Threading? • Resource Utilization
- 12. Why Threading? • Resource Utilization • Asynchronous I/O
- 13. Why Threading? • Resource Utilization • Asynchronous I/O • Shared Data or Tight Coupling
- 14. Why Threading? • Resource Utilization • Asynchronous I/O • Shared Data or Tight Coupling • Good for fine-grained parallelism
- 18. Threading Problems • Race conditions • Contention • Deadlocks
- 19. Fibers
- 20. Fibers • Pauseable/Resumable Code Blocks
- 21. Fibers • Pauseable/Resumable Code Blocks • Very lightweight
- 22. Fibers • Pauseable/Resumable Code Blocks • Very lightweight • Cooperatively scheduled
- 23. How Lightweight?
- 24. How Lightweight? Threads Fibers Time to create 1.14 sec 0.103 sec 10,000 Memory for 1000 20.6M 3.3M Simultaneous
- 26. Cooperative Scheduling • Explicit yielding and resuming
- 27. Cooperative Scheduling • Explicit yielding and resuming • No races or need for locks
- 28. Example: Fibonacci fib = Fiber.new do f1 = f2 = 1 loop do Fiber.yield f1 f1, f2 = f2, f1 + f2 end end 5.times { puts fib.resume }
- 29. Example: Fibonacci fib = Fiber.new do f1 = f2 = 1 loop do Fiber.yield f1 f1, f2 = f2, f1 + f2 end end 5.times { puts fib.resume } 1 1 2 3 5
- 30. Implicit Objects fib = Fiber.new do f1 = f2 = 1 loop do Fiber.yield f1 f1, f2 = f2, f1 + f2 end end 5.times { puts fib.resume }
- 31. Implicit Objects fib = Fiber.new do fib = Object.new f1 = f2 = 1 fib.instance_eval do loop do @f1 = @f2 = 1; Fiber.yield f1 def next f1, f2 = f2, f1 + f2 @old = @f1 end @f1, @f2 = @f1, @f2, @f1 + @f2 end @old end 5.times { puts fib.resume } end 5.times { puts fib.next }
- 32. Why Bother?
- 33. Why Bother? Aren’t blocks just implicit functions?
- 34. Why Bother? Aren’t blocks just implicit functions? Changing the semantics changes the game.
- 35. Why Bother? Aren’t blocks just implicit functions? Changing the semantics changes the game. Fibers have more flexible entry points
- 37. Synchronous Asynchronicity Have your asynchronous cake and eat it too!
- 38. Synchronous Asynchronicity Write code that looks like puts "Setting up HTTP request #1" data = async_fetch('http://www.google.com/') puts "Fetched page #1: #{data.response_header.status}" *Example from http://www.igvita.com/2009/05/13/fibers-cooperative-scheduling-in-ruby/
- 39. Synchronous Asynchronicity Write code that looks like puts "Setting up HTTP request #1" data = async_fetch('http://www.google.com/') puts "Fetched page #1: #{data.response_header.status}" Looks synchronous. Acts asynchronous. *Example from http://www.igvita.com/2009/05/13/fibers-cooperative-scheduling-in-ruby/
- 40. Events: The Hot New Thing
- 41. Events: The Hot New Thing • Node.js • Twisted (python) • EventMachine
- 42. What Is Event-Driven Programming?
- 43. What Is Event-Driven Programming?
- 44. What Is Event-Driven Programming? • Age-old Technique
- 45. What Is Event-Driven Programming? • Age-old Technique • Familiar to UI & Kernel Developers
- 46. What Is Event-Driven Programming? • Age-old Technique • Familiar to UI & Kernel Developers • Control Flow determined by Events
- 47. What Is Event-Driven Programming? • Age-old Technique • Familiar to UI & Kernel Developers • Control Flow determined by Events • Callbacks the central construct
- 48. EventMachine Example class Echo < EventMachine::Connection def post_init send_data 'Hello' end def receive_data(data) p data end end EventMachine.run { EventMachine.connect '127.0.0.1', 8081, Echo }
- 49. The Downside?
- 50. The Downside? Deeply Nested Events
- 51. The Downside? Deeply Nested Events EventMachine.run { page = EventMachine::HttpRequest.new('http://google.ca/').get page.errback { p "Google is down! terminate?" } page.callback { about = EventMachine::HttpRequest.new('http://google.ca/search?q=eventmachine').get about.callback { # callback nesting, ad infinitum } about.errback { # error-handling code } } } *Example from http://www.igvita.com/2010/03/22/untangling-evented-code-with-ruby-fibers/
- 53. The Solution? Fibers def http_get(url) f = Fiber.current http = EventMachine::HttpRequest.new(url).get # resume fiber once http call is done http.callback { f.resume(http) } http.errback { f.resume(http) } return Fiber.yield end *Example from http://www.igvita.com/2010/03/22/untangling-evented-code-with-ruby-fibers/
- 54. The Solution? Fibers def http_get(url) f = Fiber.current http = EventMachine::HttpRequest.new(url).get # resume fiber once http call is done http.callback { f.resume(http) } http.errback { f.resume(http) } return Fiber.yield end EventMachine.run do Fiber.new{ page = http_get('http://www.google.com/') puts "Fetched page: #{page.response_header.status}" page = http_get('http://www.google.com/search?q=eventmachine') puts "Fetched page 2: #{page.response_header.status}" }.resume end *Example from http://www.igvita.com/2010/03/22/untangling-evented-code-with-ruby-fibers/
- 56. Still ugly, but... • You can wrap it up in a library
- 57. Still ugly, but... • You can wrap it up in a library • In fact, someone already did
- 58. Still ugly, but... • You can wrap it up in a library • In fact, someone already did • gem install em-synchrony
- 59. Em-Synchrony Example require 'rubygems' require 'eventmachine' require 'em-synchrony' require 'em-synchrony/em-http' EventMachine.synchrony do page = EventMachine::HttpRequest.new("http://www.google.com").get p "Look Ma! No callbacks! Fetched page: #{page}" EventMachine.stop end
- 60. Where is it going?
- 61. Where is it going? • Rails 3.1 Automatic Flushing
- 62. Where is it going? • Rails 3.1 Automatic Flushing • Goliath Webserver
- 63. Where is it going? • Rails 3.1 Automatic Flushing • Goliath Webserver • Async Rails
- 64. Ruby FTW
- 65. Ruby FTW • Event-based architectures are winning
- 66. Ruby FTW • Event-based architectures are winning • Fibers => Events - Drawbacks
- 67. Ruby FTW • Event-based architectures are winning • Fibers => Events - Drawbacks • WIN!
- 68. More Resources • http://ruby-doc.org/core-1.9/classes/ Fiber.html • http://www.igvita.com/ • https://github.com/eventmachine/ eventmachine
- 69. Thank You! Kevin Ball Co-Founder and CTO fashioningchange.com [email protected] http://twitter.com/kbal11
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: \n
- #63: \n
- #64: \n
- #65: \n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n