High Performance Ruby: Evented vs. Threaded
•
1 recomendación•1,466 vistas
The document discusses the differences between evented and threaded concurrency models for Ruby applications. It explains that evented concurrency handles I/O events asynchronously while threaded concurrency uses threads to perform actual work. The document recommends using an evented model with libraries like Nginx and Trinidad to serve web applications, allowing code to be written as if it were threaded for simplicity.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a High Performance Ruby: Evented vs. Threaded
Similar a High Performance Ruby: Evented vs. Threaded (20)
Más de Engine Yard
Más de Engine Yard (19)
Último
Último (20)
High Performance Ruby: Evented vs. Threaded
- 1. High-Performance Ruby: Evented vs readed Dr Nic Williams @drnic | drnicwilliams.com | engineyard.com
- 4. midwest
- 5. midwest
- 6. kansas
- 7. kansas city
- 8. in Missouri
- 9. midwest?!
- 10. an actual safari
- 11. ________ < Safari > -‐-‐-‐-‐-‐-‐-‐-‐ ^__^ (xx)_______ (__) )/ ^ ||-‐-‐-‐-‐w | || ||
- 12. drnic cowsay
- 14. You have $
- 15. New project/rapid dev (features/$) Optimise (bugs/$) (req thru-put/$) (req latency/$)
- 16. Add resources
- 17. Resources = $ $
- 18. or even $$$$$ $ $ $$$
- 19. New project/rapid dev (features/$) how? (performance/$0) Optimise
- 21. Options •Add resources •Use resources better
- 22. you? just write code
- 23. evented -> threads -> your code
- 24. nginx -> trinidad -> web app
- 25. evented? arrange I/O
- 26. threads? actual work
- 27. you? just write code
- 28. evented -> threads -> your code
- 29. nginx -> trinidad -> web app
- 30. Options •Add resources •Use resources better
- 31. Concurrency •process concurrency •threaded concurrency •evented concurrency
- 33. Process Concurrency •1 req = 1 process = 150Mb •“100 reqs?” = 15Gb! •Orchestrated by? Kernel •Unicorn, Passenger
- 34. readed Concurrency •1 req = 1 thread = 2kb •“100 reqs?”=150Mb+200kb •Orchestrated by? Kernel •Mongrel*
- 35. 1 req = 1 thread = 2kb
- 37. evented -> threads -> your code
- 43. 2006 reality: Mongrel * Rails * Ruby1.8 --> process conc.
- 44. 20068 reality: “Rails 2.2... rst...thread safe Rails” --Pratik Naik
- 45. 20068 reality: config.threadsafe! http://guides.rubyonrails.org/configuring.html
- 46. 20068 reality: # do nothing http://www.sinatrarb.com/configuration.html
- 47. 20068 reality: Mongrel * Rails * Ruby1.8 --> process conc.
- 48. 200810 reality: “Ruby 1.9.2 is released”
- 49. 200810 reality: 1.9 has native threads!
- 50. 200810 reality: 1 thread of Ruby at a time :(
- 51. 200810 reality: GIL = Global Interpreter Lock :(
- 52. 200810 reality: GIL:( “Grumpy Gil”
- 53. 200810 reality: Mongrel * Rails * Ruby1.9 --> process conc.
- 54. “Mongrel is threaded?!” “Rails is threadsafe” but no threads...
- 56. “reads please!”
- 57. rvm install jruby rvm use jruby gem install rails rails new myapp
- 58. gem 'activerecord- jdbcsqlite3- adapter' gem 'jruby-openssl'
- 59. Mongrel * Rails * JRuby --> thread concurrency!
- 60. 1 req = 1 thread = 2kb
- 61. “How do I run JRuby/ Rails?”
- 62. How? -> trinidad -> web app
- 63. $ gem install trinidad $ trinidad --> localhost:3000
- 64. $ git clone git:// github.com/ engineyard/todo.git $ cd todo $ bundle $ rake db:migrate $ trinidad
- 65. # config.threadsafe! $ trinidad Info: max runtimes = 5
- 66. config.threadsafe! # yes! $ trinidad -e production Info: max runtimes = 1 (Thread limit 200)
- 67. 1 req = 1 thread = 2kb
- 68. And its just normal web app code!
- 69. evented -> threads -> your code
- 70. nginx -> trinidad -> web app
- 72. Web apps are* thread safe
- 73. Dr Nic’s Joy of Concurrency “Store state elsewhere; Unless its safe”
- 75. evented -> threads -> your code
- 76. nginx -> trinidad -> web app
- 77. “I came to hear good things about EventMachine”
- 78. “Evented is cool, threads are not”
- 79. “You haven’t said ‘nodejs’ once!?”
- 80. What is evented? any do something I/O? with it
- 81. cache hits req ? cache web miss app
- 82. cache hits req ? cache web miss app
- 83. req I/O work
- 84. req I/O work evented threads
- 85. req I/O work evented threads nginx trinidad
- 86. nginx vs apache
- 88. Come work with us! jruby core trinidad core rubinius core
- 89. “Be a happy developer” -> your code
- 90. -> threads -> your code
- 91. evented -> threads -> your code
- 92. nginx -> trinidad -> web app @drnic | drnicwilliams.com | engineyard.com
- 93. _____________ < Power Ruby! > -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ ^__^ (Oo)_______ (__) )/ <> ||-‐-‐-‐-‐w | || || @drnic | drnicwilliams.com | engineyard.com