Benchmark: Fixed: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values - More3

Fixed: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values - More3 (version: 4)

Compare performance between the native Object.values(obj) function vs the lodash _.values() option and a function that extracts the values of an object using a for...in loop.

Comparing performance of: unique by map, extract with deconstruct vs obj UniqueBy, extract with for...in loop vs obj UniqueBy, extract with Object.values() vs unique by map, extract with ArrayFrom

Created: 3 years ago by: Registered User

Jump to the latest result

Script Preparation code:

function uniqueBy(list, predicate, extractor) {
 	const a = new Map(list.map(l => [predicate(l), l]))
    return extractor(a)
}

function extractorDeconstruct(iterator) {
	return [...iterator.values()]
}

function extractorArrayFrom(iterator) {
 	return Array.from(iterator) 
}

function objUniqueBy(list, predicate, extractor) {
    const a = list.reduce((acc, val) => Object.assign(acc, { [predicate(val)]: val }), {})
    return extractor(a)
}

function extractValuesForIn(obj) {
   const t = [];
   for(var key in obj) { t.push(obj[key]); }
   return t;
}

function extractValuesObject(obj) {
  return Object.values(obj);
}

function makeRange(n) {
  let range = []
  for (let i = 0; i < n; i++) {
    range.push(i)
  }
  return range
}

Tests:

unique by map, extract with deconstruct
const a = Object.assign(makeRange(3000).map(i => ({ a: i, b: 1})), makeRange(1000).map(i => ({ a: i, b: 2}))) uniqueBy(a, (x) => x['a'], extractorDeconstruct)
obj UniqueBy, extract with for...in loop
const a = Object.assign(makeRange(3000).map(i => ({ a: i, b: 1})), makeRange(1000).map(i => ({ a: i, b: 2}))) objUniqueBy(a, (x) => x['a'], extractValuesForIn);
obj UniqueBy, extract with Object.values()
const a = Object.assign(makeRange(3000).map(i => ({ a: i, b: 1})), makeRange(1000).map(i => ({ a: i, b: 2}))) objUniqueBy(a, (x) => x['a'], extractValuesObject);
unique by map, extract with ArrayFrom
const a = Object.assign(makeRange(3000).map(i => ({ a: i, b: 1})), makeRange(1000).map(i => ({ a: i, b: 2}))) uniqueBy(a, (x) => x['a'], extractorArrayFrom)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
unique by map, extract with deconstruct
obj UniqueBy, extract with for...in loop
obj UniqueBy, extract with Object.values()
unique by map, extract with ArrayFrom

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36

Browser/OS: Chrome 110 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
unique by map, extract with deconstruct	4199.2 Ops/sec
obj UniqueBy, extract with for...in loop	461.1 Ops/sec
obj UniqueBy, extract with Object.values()	477.9 Ops/sec
unique by map, extract with ArrayFrom	3352.9 Ops/sec

Fixed: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values - More3 (version: 4)

Compare performance between the native Object.values(obj) function vs the lodash _.values() option and a function that extracts the values of an object using a for...in loop.

Comparing performance of: unique by map, extract with deconstruct vs obj UniqueBy, extract with for...in loop vs obj UniqueBy, extract with Object.values() vs unique by map, extract with ArrayFrom

Created: 3 years ago by: Registered User

Jump to the latest result

unique by map, extract with deconstruct

obj UniqueBy, extract with for...in loop

obj UniqueBy, extract with Object.values()

unique by map, extract with ArrayFrom

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A