by dg92

Map/Reduce/Filter/Find Vs For loop Vs For each Vs Lodash vs Ramda

484 Stars 38 Forks Last release: Not found 22 Commits 1 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


Comparing native JavaScript array methods map, reduce, filter, and find against for loop, forEach loop and lodash methods. The analysis uses basic operations and heavy data manipulation to analyze the execution speed of each method.

To run

  1. Run
    npm install
  2. Generate the data for the tests by running
    npm run seed
    • The default array is 10000 elements in length. You can create an array of a custom length by passing the desired size as an arugment, like so
      npm run seed 100000
  3. For a small data set performance report run
    npm run t:s
    • This runs the analysis on the first 5 elements of the array.
  4. For a performance report on the whole array run
    npm run t:l

To test your own function create them in the formulas.js file.

Results for small data set of array size 5 - 1000


Results for mid data set of array size 3000 - 20000


Results for large data set of array size 50000 - 1000000


Coming Soon

  1. Ramda.js test
  2. Caching (inline, warm) considerations
  3. GC considerations


  1. These results are computed using Node V8 v5.8.283.41
  2. These result does not consider the JIT, inline caching, hidden classes, deoptimizations, garbage collection, pretenuring etc.
  3. Result may vary as per env's.
  4. Red colour highlight in the above images is just for reference, will soon change.



We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.