Benchmark: Big Sample Set: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values

Big Sample Set: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values (version: 2)

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 vs bad uniqueBy, reducer has an array deconstructor

Created: 4 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 badUniqueBy(list, predicate, extractor) {
	const keyValuePairs = list.reduce((map, value) => {
     return { ...map, [predicate(value)]: value }
   }, {})
    return extractor(keyValuePairs);
}


function extractValuesForIn(obj) {
   const t = [];
   for(var key in obj) { t.push(obj[key]); }
   return t;
}

function extractValuesObject(obj) {
  return Object.values(obj);
}

function getData() {
return [{a:0,c:1},{a:1,c:1},{a:2,c:1},{a:3,c:1},{a:4,c:1},{a:5,c:1},{a:6,c:1},{a:7,c:1},{a:8,c:1},{a:9,c:1},{a:10,c:1},{a:11,c:1},{a:12,c:1},{a:13,c:1},{a:14,c:1},{a:15,c:1},{a:16,c:1},{a:17,c:1},{a:18,c:1},{a:19,c:1},{a:20,c:1},{a:21,c:1},{a:22,c:1},{a:23,c:1},{a:24,c:1},{a:25,c:1},{a:26,c:1},{a:27,c:1},{a:28,c:1},{a:29,c:1},{a:30,c:1},{a:31,c:1},{a:32,c:1},{a:33,c:1},{a:34,c:1},{a:35,c:1},{a:36,c:1},{a:37,c:1},{a:38,c:1},{a:39,c:1},{a:40,c:1},{a:41,c:1},{a:42,c:1},{a:43,c:1},{a:44,c:1},{a:45,c:1},{a:46,c:1},{a:47,c:1},{a:48,c:1},{a:49,c:1},{a:0,c:1},{a:1,c:1},{a:2,c:1},{a:3,c:1},{a:4,c:1},{a:5,c:1},{a:6,c:1},{a:7,c:1},{a:8,c:1},{a:9,c:1},{a:10,c:1},{a:11,c:1},{a:12,c:1},{a:13,c:1},{a:14,c:1},{a:15,c:1},{a:16,c:1},{a:17,c:1},{a:18,c:1},{a:19,c:1},{a:20,c:1},{a:21,c:1},{a:22,c:1},{a:23,c:1},{a:24,c:1},{a:25,c:1},{a:26,c:1},{a:27,c:1},{a:28,c:1},{a:29,c:1},{a:30,c:1},{a:31,c:1},{a:32,c:1},{a:33,c:1},{a:34,c:1},{a:35,c:1},{a:36,c:1},{a:37,c:1},{a:38,c:1},{a:39,c:1},{a:40,c:1},{a:41,c:1},{a:42,c:1},{a:43,c:1},{a:44,c:1},{a:45,c:1},{a:46,c:1},{a:47,c:1},{a:48,c:1},{a:49,c:1}]
}

Tests:

unique by map, extract with deconstruct
uniqueBy(getData(), (x) => x['a'], extractorDeconstruct)
obj UniqueBy, extract with for...in loop
objUniqueBy(getData(), (x) => x['a'], extractValuesForIn);
obj UniqueBy, extract with Object.values()
objUniqueBy(getData(), (x) => x['a'], extractValuesObject);
unique by map, extract with ArrayFrom
uniqueBy(getData(), (x) => x['a'], extractorArrayFrom)
bad uniqueBy, reducer has an array deconstructor
badUniqueBy(getData(), (x) => x['a'], extractValuesForIn);

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
bad uniqueBy, reducer has an array deconstructor

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one month ago):

LLMs can make mistakes. Check important info.

Based on the provided benchmark results and test cases, I will make an educated guess about what is being tested.

It appears that there are four different approaches to implementing the `uniqueBy` function:
1. Using `map`, `extractorDeconstruct`
2. Using `objUniqueBy` with a `for...in` loop
3. Using `map`, `extractorArrayFrom`
4. Using `objUniqueBy` with `Object.values()`

The tests seem to be comparing the performance of these different approaches.

Based on the benchmark results, it appears that:

* The "unique by map, extract with deconstruct" approach is the fastest, with an average execution time per second of 110758.2109375.
* The "obj UniqueBy, extract with Object.values()" and "obj UniqueBy, extract with for...in loop" approaches are significantly slower, with average execution times of around 45000-12000 seconds per second.

The other two tests ("unique by map, extract with ArrayFrom" and "bad uniqueBy, reducer has an array deconstructor") have relatively low execution times, but it's unclear what the specific performance characteristics of these approaches are without more information.

Without more context or information about the implementation details, it is difficult to provide a definitive answer. However, based on the provided benchmark results, it appears that the "unique by map, extract with deconstruct" approach is likely the fastest and most efficient solution.

Latest run results:

Run details: (Test run date: 3 years ago)

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

Browser/OS: Chrome 93 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
unique by map, extract with deconstruct	110758.2 Ops/sec
obj UniqueBy, extract with for...in loop	12161.0 Ops/sec
obj UniqueBy, extract with Object.values()	12216.4 Ops/sec
unique by map, extract with ArrayFrom	79450.8 Ops/sec
bad uniqueBy, reducer has an array deconstructor	44945.5 Ops/sec

Related benchmarks:

Big Sample Set: Performance of uniqueBy using new Map or reducing to an object, also comparing for..in and Object.values for extracting values (version: 2)

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 vs bad uniqueBy, reducer has an array deconstructor

Created: 4 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

bad uniqueBy, reducer has an array deconstructor

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one month ago):