Benchmark: Lodash Pick vs Native destructuring vs Manual

HTML Preparation code:

<script src="https://cdn.jsdelivr.net/npm/lodash@4.17.11/lodash.min.js"></script>

Script Preparation code:

var arr = [];
var object = { 
	type: 'aaa',
    subtype: 'bbb',
    card_last4:'bbb',
    card_type:'bbb',
    card_exp_month:'bbb',
    card_exp_year:'bbb',
    card_country:'bbb',
    foo: 'bar'
};
for (var i = 0; i <= 100000; i++) { arr.push(object); }

Tests:

Lodash
arr.map(function (element) { return _.pick( element, 'type', 'subtype', 'card_last4', 'card_type', 'card_exp_month', 'card_exp_year', 'card_country', 'something' ); });
Native
arr.map(function (element) { const { type, subtype, card_last4, card_type, card_exp_month, card_exp_year, card_country, something } = element; return { type, subtype, card_last4, card_type, card_exp_month, card_exp_year, card_country, something }; });
Manual pick
const props = [ "type", "subtype", "card_last4", "card_type", "card_exp_month", "card_exp_year", "card_country", "something" ]; arr.map(function (element) { const res = {}; for(let prop of props){ res[prop] = element[prop] } return res; });

Historical Performance Data aggregated from 30 community runs

Desktop Results:

Chrome 25 runs

Native

265/s

Manual pick

57/s

Lodash

8/s

Fastest: Native (33.5x faster)

View exact numbers

✓ Native: 265 ops/sec
• Manual pick: 57 ops/sec
• Lodash: 8 ops/sec

Firefox 5 runs

Native

163/s

Manual pick

18/s

Lodash

3/s

Fastest: Native (48.9x faster)

View exact numbers

✓ Native: 163 ops/sec
• Manual pick: 18 ops/sec
• Lodash: 3 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Lodash
Native
Manual pick

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 7 months ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0

Browser/OS: Firefox 146 on Windows

View result in a separate tab

Native

497/s

Manual pick

29/s

Lodash

4/s

View exact numbers

Test name	Executions per second
✓ Native	497 Ops/sec
Manual pick	29 Ops/sec
Lodash	4 Ops/sec

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

LLMs can make mistakes. Check important info.

**Overview**

The provided JSON represents a benchmarking test for comparing the performance of three approaches to extract specific properties from an object in JavaScript: Lodash's `pick` function, native destructuring, and manual property extraction.

**Benchmark Definition**

The benchmark definition consists of three individual test cases:

1. **Lodash**: Uses Lodash's `pick` function to extract specific properties from the object.
2. **Native**: Utilizes native destructuring syntax to extract properties from the object.
3. **Manual pick**: Manually extracts properties using a loop and the `in` operator.

**Options Compared**

The three approaches are compared in terms of their performance, which is measured by the number of executions per second on a given test case (arr.map function).

**Pros and Cons**

1. **Lodash (`pick` function)**:
	* Pros: Lodash provides a convenient and flexible way to extract properties from objects.
	* Cons: It may introduce additional overhead due to the library's execution time.
2. **Native destructuring**:
	* Pros: Native destructuring is fast, concise, and widely supported in modern browsers.
	* Cons: May require more cognitive load for developers unfamiliar with this syntax.
3. **Manual pick (loop)**:
	* Pros: Manually extracting properties using a loop can be efficient and easy to understand for some developers.
	* Cons: Can be time-consuming and error-prone, especially for large objects.

**Library and Purpose**

The Lodash library is used in the "Lodash" test case. Its primary purpose is to provide a set of functional programming helpers, including the `pick` function.

**Special JS Feature or Syntax**

Native destructuring syntax (e.g., `{ type, subtype, ... } = element;`) is used in the "Native" test case. This feature allows developers to extract multiple properties from an object into separate variables in a single statement.

**Other Alternatives**

If native destructuring is not supported by older browsers or environments, alternative approaches can be considered:

* Using `Object.keys()` and `Array.prototype.map()`
* Employing a library like underscore (not Lodash) or moment.js
* Utilizing other JavaScript object manipulation techniques

Please note that the performance differences between these approaches may vary depending on the specific use case, browser versions, and system configurations.

I hope this explanation helps you understand the benchmarking test and the pros and cons of each approach!

Lodash Pick vs Native destructuring vs Manual (version: 0)

Compare _.pick vs native destructuring

Comparing performance of: `Lodash vs Native vs Manual pick`

Created: 6 years ago by: Guest

Go to the latest result

Lodash

Native

Manual pick

Historical Performance Data aggregated from 30 community runs

Desktop Results:

Chrome 25 runs

Firefox 5 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Lodash Pick vs Native destructuring vs Manual (version: 0)

Compare _.pick vs native destructuring

Comparing performance of: Lodash vs Native vs Manual pick

Created: 6 years ago by: Guest

Go to the latest result

Lodash

Native

Manual pick

Historical Performance Data aggregated from 30 community runs

Desktop Results:

Chrome 25 runs

Firefox 5 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Related benchmarks

Comparing performance of: `Lodash vs Native vs Manual pick`