Run results for: Compount Mapping and Sorting (lodash vs native)

Run details:

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

Browser: Chrome 125

Operating system: Windows

Device Platform: Desktop

Date tested: 5 months ago

Test name	Executions per second
Native JS map and sort	1.2 Ops/sec
lodash sortby(native map)	0.7 Ops/sec
lodash chain map, and sortBy	3856136.0 Ops/sec

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.21/lodash.min.js" integrity="sha512-WFN04846sdKMIP5LKNphMaWzU7YpMyCU245etK3g/2ARYbPK9Ub18eG+ljU96qKRCWh+quCY7yefSmlkQw1ANQ==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>

Script Preparation code:

var arr = [];
for (var i = 0; i < 1_000_000; i++) {
  arr.push({ value: Math.random() });
}

Tests:

Native JS map and sort
arr.map(item=>({...item, negated_square: -item.value*item.value})).sort((a, b) => a.negated_square - b.negated_square);
lodash sortby(native map)
_.sortBy(arr.map(item=>({...item, negated_square: -item.value*item.value})), 'negated_square');
lodash chain map, and sortBy
_.chain(arr).map(item=>({...item, negated_square: -item.value*item.value})).sortBy('negated_square');

Run results for: Compount Mapping and Sorting (lodash vs native)

_.sortBy vs _.orderBy vs JS sort

Native JS map and sort

lodash sortby(native map)

lodash chain map, and sortBy