A small benchmark test for ruby ORMs.
Latest commit 0db5f9e Oct 6, 2016 @jeremyevans Refactor JSON support
Only create JSON-related tables/models if JSON is supported.

Restore faster creation of existing rows before benchmarks.

Send debug logs to stderr instead of stdout.

Rename JSON benchmarks to mention JSON instead of Hash.

Remove foreign key usage in sequel benchmarks, since they weren't used in active record benchmarks.



simple_orm_benchmarker is a simple script to benchmark ruby ORMs.  It
currently supports ActiveRecord, Sequel, and Mongoid.


To use this, you first need to copy db.yml.example to db.yml, and modify it


Then you can run the benchmarking via:

  ruby simple_orm_benchmark.rb -a
  ruby simple_orm_benchmark.rb sequel-postgresql
  ruby simple_orm_benchmark.rb -l 4 activerecord-mysql
  ruby simple_orm_benchmark.rb -l 6 -g activerecord-sqlite sequel-sqlite


* -a will test all configurations in the db.yml configuration file.
* -l is the testing level.  It's designed to be logrithmic, with a level 6
  test taking about twice as long as a level 5.  The default level is 5.
* -g will disable garbage collection during the test, to measure the amount
  of garbage the test generates.

You can list one or more configurations to test as arguments.  The
arguments should match keys in the hash parsed from the yaml file.

The output of the benchmark is in CSV, with columns in the following order:

configuration_name: Name of configuration
level: Testing level
benchmark_name: Name of benchmark
user_cpu_time: Amount of user CPU time
system_cpu_time: Amount of system CPU time
total_cpu_time: Amount of total CPU time
elapsed_real_time: Amount of actual/real/wallclock time
kb_of_memory_used: Difference in process memory usage from the benchmark
transaction_used: Whether a transaction was used

Most tests are run both inside of and outside of a transaction, so you get
results both ways.

There are also some JSON tests, which are run on databases that support JSON functions.
Note that SQLite doesn't enable JSON functions by default, you have to compile the json1
extension into SQLite and make sure your ruby sqlite3 library correctly uses that version
of SQLite.  Alternatively, you can use the amalgalite adapter when testing on Sequel,
because recent versions enable the json1 extension.


For easier comparison of different configurations, you can use the
results_aggregator.rb script:

  ruby simple_orm_benchmark.rb sequel-sqlite activerecord-sqlite > r.txt
  ruby results_aggregator.rb r.txt

That will output CSV, with columns in the following order:


Using this you can see comparitive results easily, not just for different
ORMs, but also for different databases with the same ORM.



Jeremy Evans (code@jeremyevans.net)

Contact me if you have questions about this benchmark script.  Contributions of
new benchmark tests are appreciated.

Thanks to tim.linquist@gmail.com (timo3377) for sequel-benchmark and
activerecord-benchmark, on which simple_orm_benchmark is based.