mathjs/benchmark
greenkeeper[bot] c5971b371a Update standard to the latest version 🚀 (#1226)
* chore(package): update standard to version 12.0.0

* update to new lint version with --fix

I believe this mainly adds whitespace to `{}`'s.

* Replace assert.equal with assert.strictEqual

This breaks a lot of tests which I will endevour to fix in the next
commits.

* Fix most errors due to assert.strictEquals

Some instances of `strictEquals` are replaced by `deepEquals`.
`toString` has been used to make some string comparisions explicit.
Tests will still fail untill #1236 and #1237 are fixed.

* Fix assertion erros due to -0

With node 10, assert.strictEqual no longer considers `0 === -0`.
I missed these first time round as I was using node 8.

* Put toString correct side of bracket

I was converting the constructor to a string rather
than the result of the computation. Oops.

* Fixed #1236: quantileSeq has inconsistant return

* Update package-lock

* Fixed #1237: norm sometimes returning a complex number instead of number

* Fix cli tests

* More changes for standardjs, and fixes in unit tests
2018-09-08 16:33:58 +02:00
..

Benchmarks

This directory contains benchmarks which can be used when working on performance improvements of math.js.

How to run

First build the source code once:

$ npm install
$ npm run build

To run all benchmarks:

$ node index.js

To run a single set of benchmarks:

$ node expression_parser.js

Python benchmarks

Install python, and the python library numpy, then run the benchmarks:

$ python matrix_operations_python.py

Octave benchmarks

For matrix operations, there is a small benchmark for Octave. Open Octave, run the script matrix_operations_octave.m

To do

  • use larger matrix, like 250x250 instead of 25x25
  • Compare expression parsers
    • math.js
    • expr-eval
    • jsep
    • math-expression-evaluator