Run results for: Ramda vs. Lodash vs Natice (filter, find)

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36

Browser: Chrome 133

Operating system: Windows

Device Platform: Desktop

Date tested: one year ago

Benchmark engine: Benchmark.js

Native find

2.2M/s

Lodash find

534K/s

Native filter

29K/s

Ramda find

20K/s

Lodash filter

563/s

Ramda filter

560/s

View exact numbers

Test name	Executions per second
✓ Native find	2,167,057 Ops/sec
Lodash find	533,871 Ops/sec
Native filter	29,379 Ops/sec
Ramda find	20,108 Ops/sec
Lodash filter	563 Ops/sec
Ramda filter	560 Ops/sec

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/ramda/0.25.0/ramda.min.js"></script>
<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.5/lodash.min.js'></script>

Script Preparation code:

var fp = _.noConflict();

var data = _.range(10000).map(function(i) {
  return {counter: i}
});

function isOdd(num) {
  return num % 2 === 1;
}

Tests:

Lodash filter
var result = _.filter(data, isOdd);
Ramda filter
var result = R.filter(isOdd, data);
Native filter
var result = data.filter(({counter}) => isOdd(counter));
Lodash find
var result = _.find(data, {counter: 859});
Ramda find
var result = R.find(R.propEq('counter', 859), data);
Native find
var result = data.find(({counter}) => counter === 859);