Run results for: native find vs lodash _.find vs map+indexOf vs findIndex

Run details:

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

Browser: Chrome 97

Operating system: Windows

Device Platform: Desktop

Date tested: 2 years ago

Test name	Executions per second
array find	12791618.0 Ops/sec
_.find	3944434.0 Ops/sec
map+indexOf	14384.8 Ops/sec
findIndex	12018581.0 Ops/sec
new Map object	1343.7 Ops/sec
already existing Map object	11401984.0 Ops/sec

HTML Preparation code:

<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.11/lodash.core.js"></script>

Script Preparation code:

var users = [
  { user: 'joey',  age: 32, id: 0 },
]

for(var i=1; i < 10000; i++) {
  users.push({ user: 'ross', age: 41, id: i, managerId: i-1 });
}

var usersExistingMap = new Map();
users.map(u => {
	usersExistingMap.set(u.id, u);
});

Tests:

array find
// Native users.find(function (o) { return o.id = 41; })
_.find
_.find(users, function (o) { return o.id = 41; })
map+indexOf
users.map(o => o.id).indexOf(41)
findIndex
users.findIndex(o => o.id === 41)
new Map object
let usersMap = new Map(); users.map(u => { usersMap.set(u.id, u); }); usersMap.has(41);
already existing Map object
usersExistingMap.has(41);

Run results for: native find vs lodash _.find vs map+indexOf vs findIndex

Compare the new ES6 spread operator with the traditional concat() method

array find

_.find

map+indexOf

findIndex

new Map object

already existing Map object