Benchmark: Get object Vanilla VS Lodash

HTML Preparation code:

<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.5/lodash.min.js'></script>

Script Preparation code:

var fullObject = {
  a: {
    b: {
      c: 'value'
    }
  }
}

var emptyObject = {}

Tests:

Nested - Try catch fullObject
try { var c = fullObject.a.b.c } catch(e) {}
Nested - Lodash get() on fullObject
var c = _.get(fullObject, 'a.b.c')
Nested - Inline validation on fullObject
var c = fullObject?.a?.b?.c
First - Try catch fullObject
try { var a = fullObject.a } catch(e) {}
First - Lodash get() on fullObject
var a = _.get(fullObject, 'a')
First - Inline validation on fullObject
var a = fullObject?.a

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Nested - Try catch fullObject
Nested - Lodash get() on fullObject
Nested - Inline validation on fullObject
First - Try catch fullObject
First - Lodash get() on fullObject
First - Inline validation on fullObject

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

Let's break down the benchmark and explain what's being tested.

**Benchmark Description**

The benchmark compares the performance of three approaches to access nested object properties in JavaScript:

1. **Try-Catch Block**: Using a try-catch block to access nested properties.
2. **Lodash `get()` method**: Using the Lodash library's `get()` method to access nested properties.
3. **Inline Validation with Optional Chaining**: Using the optional chaining operator (`?.`) to access nested properties.

**Options Compared**

The benchmark tests four individual test cases, each comparing one of the three approaches:

* "First - Try catch fullObject"
* "Nested - Try catch fullObject"
* "First - Lodash get() on fullObject"
* "Nested - Lodash get() on fullObject"

These test cases aim to isolate the performance differences between the three approaches.

**Pros and Cons of Each Approach**

1. **Try-Catch Block**:
	* Pros: Can provide a safe way to access nested properties by catching any errors that may occur.
	* Cons: Can introduce additional overhead due to the try-catch block, especially if not necessary for performance-critical code.
2. **Lodash `get()` method**:
	* Pros: Provides a convenient and efficient way to access nested properties, especially when working with complex objects or arrays.
	* Cons: Requires including an external library (Lodash), which may add overhead due to the HTTP request or download time.
3. **Inline Validation with Optional Chaining**:
	* Pros: Provides a lightweight and modern way to access nested properties without introducing try-catch blocks or external libraries.
	* Cons: May not be compatible with older browsers that don't support optional chaining.

**Library Used**

The Lodash library is used in the benchmark to provide the `get()` method. Lodash is a popular utility library for JavaScript that provides various functions for tasks like array manipulation, object manipulation, and more.

**Special JS Feature or Syntax**

Optional Chaining (`?.`) was introduced in ECMAScript 2020 (ES2020) as a part of the standard language. It allows you to access nested properties without throwing an error if the property does not exist.

**Alternatives**

Other alternatives for accessing nested properties include:

* Using `in` operator to check if a property exists before attempting to access it.
* Using `hasOwnProperty()` method on objects to check if a property exists.
* Using ` bracket notation` (e.g., `obj['a']['b']`) or dot notation with optional chaining (`obj?.a?.b`) for more complex cases.

However, these alternatives may not provide the same level of convenience and performance as using Lodash's `get()` method or optional chaining.

Latest run results:

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

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

Browser/OS: Chrome 80 on Mac OS X 10.14.4

View result in a separate tab

Test name	Executions per second
Nested - Try catch fullObject	9591814.0 Ops/sec
Nested - Lodash get() on fullObject	1548401.8 Ops/sec
Nested - Inline validation on fullObject	9441778.0 Ops/sec
First - Try catch fullObject	9512991.0 Ops/sec
First - Lodash get() on fullObject	2328738.2 Ops/sec
First - Inline validation on fullObject	9892062.0 Ops/sec

Related benchmarks:

Get object Vanilla VS Lodash (version: 0)

Comparing performance of: Nested - Try catch fullObject vs Nested - Lodash get() on fullObject vs Nested - Inline validation on fullObject vs First - Try catch fullObject vs First - Lodash get() on fullObject vs First - Inline validation on fullObject

Created: 4 years ago by: Registered User

Jump to the latest result

Nested - Try catch fullObject

Nested - Lodash get() on fullObject

Nested - Inline validation on fullObject

First - Try catch fullObject

First - Lodash get() on fullObject

First - Inline validation on fullObject

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):