Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Similar a Rails Hardware (no conclusions!)
Similar a Rails Hardware (no conclusions!) (20)
Último
Último (20)
Rails Hardware (no conclusions!)
- 1. You need different kinds of performance
- 2. You need different kinds of performance Production
- 3. You need different kinds of performance Production Development
- 4. Production
- 5. core 1 core 2 core 3 core 4 … time core time
- 6. core 1 core 2 core 3 core 4 … time core time
- 7. core 1 core 2 core 3 8 core 4 … time core 5 time
- 8. Great max RPM == high performance?
- 9. 100 ppl x 60 km/h Economical and efficient
- 10. User cares about performance of HIS request only 1 x 300 km/h
- 11. …especially in ruby Time, s C GNU gcc 1.07 Java 6 -server 1.55 Haskell GHC 2.16 Scala 2.22 Lisp SBCL 2.67 C# Mono 2.95 OCaml 3.35 Clojure 5.32 Erlang HiPE 13.17 Python 3 28.07 Ruby 1.9 65.14 by http://shootout.alioth.debian.org Computer Language Benchmarks Game
- 12. Garbage collection (GC) core 1 core 2 core 3 core 4 … time Actual productive work
- 13. Ideally, GC should occur between requests (during idle time) core 1 core 2 core 3 core 4 … time what USER cares about
- 14. Tweaking GC results in… 30%–50% better throughput AND response times http://www.rubyenterpriseedition.com/ documentation.html#_garbage_collector_performance_tuning
- 17. Roundtrip to Moscow 50ms … Europe +100ms … US +100ms
- 18. In development
- 19. In development You reinitialize Rails stack frequently You use a single CPU core most of the time
- 20. In development You reinitialize Rails stack frequently (unless using Spork etc) You use a single CPU core most of the time
- 21. In development You reinitialize Rails stack frequently (unless using Spork etc) You use a single CPU core most of the time (unless using parallel_specs, hydra etc)
- 22. Rails’ own test suite
- 23. Rails’ own test suite ~% git clone git://github.com/rails/rails.git Cloning into rails... ~% cd rails ~/rails[master]% git checkout v3.0.7 Note: checking out 'v3.0.7'. … HEAD is now at 2c32601... bumping version for release ~/tmp/rails[tag: v3.0.7]% bundle install Fetching source index for http://rubygems.org/ … Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed. ~/tmp/rails[tag: v3.0.7]% time bundle exec rake test | tee out.txt 2>&1
- 24. MySQL 5.5 PostgreSQL 9 SQLite 3.6.16+ memcached mysql2 gem 0.2.x (not 0.3.x) …
- 25. ~/rails[tag: v3.0.7]% cat out.txt| grep 'errors' 2294 tests, 9629 assertions, 0 failures, 0 errors 419 tests, 1171 assertions, 0 failures, 0 errors 2981 tests, 12075 assertions, 0 failures, 0 errors 72 tests, 142 assertions, 0 failures, 0 errors 200 tests, 515 assertions, 0 failures, 0 errors 273 tests, 773 assertions, 0 failures, 0 errors 2483 tests, 7646 assertions, 0 failures, 0 errors 2471 tests, 7634 assertions, 0 failures, 0 errors 2443 tests, 7555 assertions, 0 failures, 0 errors 2522 tests, 7865 assertions, 0 failures, 0 errors 28 tests, 33 assertions, 0 failures, 0 errors 6 tests, 15 assertions, 0 failures, 0 errors 7 tests, 14 assertions, 0 failures, 0 errors 1 tests, 0 assertions, 0 failures, 0 errors 1 tests, 1 assertions, 0 failures, 0 errors 10 tests, 12 assertions, 0 failures, 0 errors 6 tests, 7 assertions, 0 failures, 0 errors 13 tests, 18 assertions, 0 failures, 0 errors 5 tests, 9 assertions, 0 failures, 0 errors 1 tests, 2 assertions, 0 failures, 0 errors 3 tests, 6 assertions, 0 failures, 0 errors 21 tests, 22 assertions, 0 failures, 0 errors 4 tests, 28 assertions, 0 failures, 0 errors 5 tests, 7 assertions, 0 failures, 0 errors 4 tests, 4 assertions, 0 failures, 0 errors 13 tests, 18 assertions, 0 failures, 0 errors 5 tests, 5 assertions, 0 failures, 0 errors 3 tests, 3 assertions, 0 failures, 0 errors 1 tests, 1 assertions, 0 failures, 0 errors 4 tests, 4 assertions, 0 failures, 0 errors 37 tests, 69 assertions, 0 failures, 0 errors 35 tests, 305 assertions, 0 failures, 0 errors … (continues)
- 26. ~/rails[tag: v3.0.7]% cat out2.txt | ruby -ne 'next unless $_ =~ /^((d+) (tests|assertions|failures|errors)(?:, )?) {4}$/; $_.split(", ").each { |pair| count, name = *pair.split(" "); @totals ||= {}; @totals[name] ||= 0; @totals[name] += count.to_i }; print "r"+@totals.map { | key, val| "#{key} #{val}"}.join(", "); STDOUT.flush; END {puts}' failures 0, tests 16658, errors 0, assertions 56316
- 27. ## ruby -ne '...' next unless $_ =~ /^((d+) (tests|assertions|failures|errors)(?:, )?){4}$/ $_.split(", ").each do |pair| count, name = *pair.split(" ") @totals ||= {} @totals[name] ||= 0 @totals[name] += count.to_i end print "r"+@totals.map { |key, val| "#{key} #{val}"}.join(", "); STDOUT.flush; END {puts}
- 30. CC (attribution) photos bus http://www.flickr.com/photos/futurepastnow/2972823328 ferrari http://www.flickr.com/photos/dontthinkfeel/200793214/ obie http://www.flickr.com/photos/seanosh/2544491971 earth NASA rope walking http://www.flickr.com/photos/envizion/470658414
Notas del editor
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- simplest of all, but it does not tell the whole story\n
- This is where cloud infrastructure may seem inferior.\n
- \n
- you should benchmark representative code to be relevant, not calculating Pi\n
- \n
- (and less frequently too)\n
- What’s the word on tweaking GC in ruby 1.9?\n
- free + lots of promo codes\nyou want to track queueing time as well \nUse REE to get GC info\nOutlier requests analysis is not so useful, to me it always happens during the times of I/O shortage, not CPU shortage\nAn opportunity to create a more focused service\nRecall cloud hosting\n\nIn real application, there may be no single point responsible for the slowdown\n"Death by a thousand cuts" is the toughest one to combat\nExcept we can jump to the latests CPUs\nTurbo boost, eh? Perhaps underutilized Xeons are the way to go to get the absolute max\nA particular problem with Rails 3 where middleware is slightly slower, activerecord is slightly slower, who knows what else slightly slower\nThis is what the adoption rate slow\nView helpers are slow when there are many of them\nSerialization is slow\nHappens when loading structured data from memcached\nLoad strings?\n
- \n
- Why Basecamp feels sluggish\nWhy Rails 3 is adopted slowly\nWhy streaming in Rails 3.1 may change the game\n
- \n
- Chances are, you will be loading a single core\nYou need fastest startup time - running rake tasks, tests, generators, console, restarting the server\nThe way rubygems are written, every 'require' inspects LOADPATH\nRuby 1.9.2 is not that good for fast startups\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n