Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
README.md

fork

jrochkind's fork of threez's original:

  • commented out patron tests, couldn't get patron to install on my machine
  • added net-http-persistent test
  • fixed httpclient test to not init in inner loop
  • i personally don't use the java tests and apache bench tests you get from make. I don't think I've broken em. But I just test with bundle install and ruby test.rb number url under ruby 1.9.3
  • I added some features to test.rb for multi-threaded testing: set in env variables CONCURRENCY=n and PER_THREAD=m. As well as a env SKIP=comma-seperated test file names.

See http://bibwild.wordpress.com/2012/04/30/ruby-http-performance-shootout-redux/ for details and findings

See github compare for diff between my fork and original.

Original README

When you deal with a lot HTTP requests in your application, you want to have them as fast and light as possible. Also one want to take advantage of the HTTP keep alive functionality to reduce the number of reconnects to the hosting server if possible. Gzipping and other techniques are very welcome also. All this is especially interesting if your infrastructure is relying on this http communication heavily. HTTP is very good in providing a stable and flexibel solution, but sometimes suffers from the performance of native protocols.

The project I'm currently working on involves a lot of internal http communication. Therefore I wanted to have a look on the http client performance. Because the client I used is implemented in Ruby I mostly compare ruby libs and versions. I also implemented a Java based http client implementation along with the benchmark to compare the results to a completely different setup. As a round up I added a test with apache bench and httperf to see what a normal benchmark would tell us in time and throughput.

The tests consists of two things:

  • The first step is to download a 16KB json asset from the remote server. The server in my tests is a separate system directly linked with a cat.6 gigabit ethernet cable. The remote is a 2.26 GHz Intel Core 2 Duo, 8 GB 1067 MHz DDR3. The main focus is on benchmarking library and stack efficiency.
  • The second step is to parse these incoming data and grep a value and check this value for correctness. Sure, this is not possible in the case of apache bench and httperf.

For the json parsing i used the yajl-ruby gem and included the json gem wrapper to leverage the json parser of yajl when possible and provided though the library. If the library doesn't have direct support for json parsing I implemented it by my self in a competitive manner.

In the Java world i used the json simple project from google code. The performance is nearly comparable to what ruby offers. I started the java test both in server and client mode.

I used the apache web server that is bundled with MacOSX (Version 10.6.7 - Apache/2.2.17).

I use sessions if the library provides it. The test will be executed 10.000 times.

The results and objective of the benchmark is to measure the user and system time used during the execution of the requests and the throughput that could be generated.

The whole test scenario can be found on github. To run the test suite on your mashine simple run:

make

The results I found out during my observations is pretty impressive. Ruby actually doesn't have to hide itself in these benchmarks when using the native libraries that are empowered using libcurl. Here are the facts:

  • using Java one can achieve around 7,3 MB/s and approximately 460 requests/s
  • using Ruby around 13,9 MB/s and approximately 876 requests/s are possible

Native applications without json parsing:

  • apache bench produces less throughput (12,7 MB/s) than Ruby and approximately 766 requests/s
  • the best results can be achieved using httperf around 18 MB/s and approximately 1091 requests/s

Ruby has a bunch of native http libraries that perform very well when doing a lot of blocking http calls. For me curb and patron are the best choise. Even if they may miss some functionality (certificate authentication in patron) or convenience (curb sessions). Java has also good numbers but can not compete with the native libraries on the same level.

Throughput MB/sReal Time (s)User + System Time (s)All Data

Something went wrong with that request. Please try again.