These benchmarks are uselessly bad: - The client connections are run without concurrency, serially, on the same machine: https://github.com/brianhempel/isrubyf

These benchmarks are uselessly bad: - The client connections are run without concurrency, serially, on the same machine: https://github.com/brianhempel/isrubyfastyet/blob/master/runner/benchmarks/rails/requests_per_second_benchmark.rb#L16 https://github.com/brianhempel/isrubyfastyet/blob/master/run... - The JIT is only given 3 seconds to warm up: https://github.com/brianhempel/isrubyfastyet/blob/master/runner/benchmarks/rails/requests_per_second_benchmark.rb#L12 https://github.com/brianhempel/isrubyfastyet/blob/master/run... -- HotSpot kicks ass, but not after only 3 seconds of serially issued requests. - By running the tests single-threaded, they're throwing away one of the major wins of the JVM -- low overhead concurrency.