benchmark each release of a node module published on npm against each other release using a small command line tool
npm install npmbench
Example: benchmarking the
redis package, and running the file
multi_bench.js against each release:
npmbench redis multi_bench.jsOps/sec***** v0.0.1******* v0.0.2******** v0.0.3**** v0.0.4********** v0.0.5
A command line tool to examine your code's performance over various releases.
Your bench should output something like this (even just one line that says
888 ops/sec will work just fine):
[... whatever test output you like ...] 999.9 ops/sec[... whatever test output you like ...] 999.9 ops/sec[... whatever test output you like ...] 999.9 ops/sec
Summary: there must be at least one line, and the 2nd to last whitespace separated word must be a number representing the ops/sec.
npmbench-moduleName@x.y.z.txt. It skips running a given bench if there is already a .txt file there for it.
Why is this nice? Makes it easy to write your own parser for the output.