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

Run details:

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

Browser: Chrome 88

Operating system: Windows 8.1

Device Platform: Desktop

Date tested: 3 years ago

Test name	Executions per second
Lodash filter	283.7 Ops/sec
Ramda filter	315.4 Ops/sec
Native filter	324.1 Ops/sec
Lodash find	56712.8 Ops/sec
Ramda find	3778.2 Ops/sec
Native find	276978.2 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);

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

Compares performance on the same tasks using Lodash vs Ramda vs Native.

Lodash filter

Ramda filter

Native filter

Lodash find

Ramda find

Native find