View the site: www.isrubyfastyet.com
- "ruby speed" is 1/8 as popular as "ruby tutorial"
- "ruby speed" is 1/5 as popular as "ruby language"
- "ruby speed" is 1/2 as popular as "python speed"
You need the gtimeout command from GNU Coreutils. Easy peasy with Homebrew on OS X.
brew install coreutils
You also need phantomjs if you would like to transform the Rails frontend to a static site.
brew install phantomjs
The benchmark suite runner currently needs to start under a fork-enabled ruby (i.e., not JRuby).
# run the entire benchmark suite (~3.5 hours on my box, more for the first run)
cd runner
rake
# see how the latest results compare to the median of the 5 previous
rake variability
Individual benchmarks can be run on any Ruby implementation (fork not required). If you want to run a benchmark individually...
# switch to the ruby version you want
rvm jruby-head
# navigate to the benchmark folder
cd runner/benchmarks/rails
# you may have to do some bundling here (not shown)
# then simply execute the benchmark
ruby requests_per_second_benchmark.rb
Writing a new benchmark is easy. The individual benchmarks are simply Ruby files in runner/benchmarks ending with *benchmark.rb. Simply author a new file in the benchmarks folder, such as "benchmarks/pure_ruby_gzip/compression_benchmark.rb", and make sure the last line to standard out is the benchmark result with units, like 123456 KB compressed per second.
To skip cool-down pauses and only do one run of each benchmark...
export IRFY_DEV_MODE=true
Tests need Ruby >= 1.9, though the benchmark suite can run under 1.8.7.
# to test the front-end app
cd isrubyfastyet.com
bundle install
rake
# to test the shared models
gem install rspec
rspec spec/