Benchmark: native findIndex vs lodash findIndex test

HTML Preparation code:

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

Script Preparation code:

var users = [
  { 'user': 'joey',  'cA': {"currency": "wadd","value": 0}, 'TA': {"currency": "wadd","value": 0}, 'PA': {"currency": "wadd","value": 0} },
  { 'user': 'ross',  'cA': {"currency": "wadd","value": 0}, 'TA': {"currency": "wadd","value": 0}, 'PA': {"currency": "wadd","value": 0},  'age': 31 },
  { 'user': 'chandler', 'cA': {"currency": "wadd","value": 0}, 'TA': {"currency": "wadd","value": 0}, 'PA': {"currency": "wadd","value": 0},'age': 30 },
  { 'user': 'jessika','cA': {"currency": "wadd","value": 0}, 'TA': {"currency": "wadd","value": 0}, 'PA': {"currency": "wadd","value": 0}, 'age': 21 },
  { 'user': 'amanda', 'cA': {"currency": "wadd","value": 0}, 'TA': {"currency": "wadd","value": 0}, 'PA': {"currency": "wadd","value": 0},'age': 17 }
]

Tests:

Native findIndex
users.findIndex(u => u.user === 'jessika')
_.findIndex
_.findIndex(users, u => u.user === 'jessika')

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Native findIndex
_.findIndex

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

**What is being tested?**

The provided JSON represents two individual test cases: `native findIndex` and `_.findIndex`. The benchmark measures the performance of these two functions in finding an element within an array.

**Options compared:**

1. **Native `.findIndex()`**: This function is built-in to JavaScript arrays, using a V8 engine-specific algorithm.
2. **Lodash's `_findIndex()`**: This is a utility function from the Lodash library, which provides a higher-order function for finding the index of a value within an array.

**Pros and Cons:**

* **Native `.findIndex()`**:
	+ Pros:
		- Native implementation, optimized for performance.
		- Less memory overhead due to not loading a separate library.
	+ Cons:
		- Limited functionality, only works with native arrays.
		- Can be slower than Lodash's implementation if the array is very large.
* **Lodash's `_findIndex()`**:
	+ Pros:
		- More flexible and widely applicable (not limited to native arrays).
		- May be faster for large arrays due to optimized algorithms.
	+ Cons:
		- Requires loading an additional library, which can increase memory overhead.
		- Can introduce additional latency due to the need to import and initialize Lodash.

**Library used:**

* **Lodash**: A popular JavaScript utility library that provides a wide range of functions for tasks like array manipulation, string processing, and more. In this case, the `_findIndex()` function is used to find the index of an element within an array.

**Special JS feature or syntax:**

None mentioned in the provided JSON.

**Other considerations:**

* **Array size**: The performance difference between native `.findIndex()` and Lodash's `_findIndex()` may become more noticeable for very large arrays. For smaller arrays, the difference might be negligible.
* **Browser and version**: The benchmark results are specific to a particular browser (Chrome 115) and operating system (Windows). Running the benchmark on different browsers or operating systems may yield different results.

**Alternative approaches:**

1. **Using `indexOf()` instead of `.findIndex()```**: While not recommended for most use cases, using `indexOf()` can be faster than `.findIndex()` due to its native implementation.
2. **Using other array algorithms**: Depending on the specific requirements, other array algorithms like `.filter()`, `.map()`, or `.forEach()` might be more suitable for finding an element within an array.

Keep in mind that these alternatives may have their own trade-offs and performance characteristics, which should be considered when choosing an approach.

Latest run results:

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

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

Browser/OS: Chrome 115 on Windows

View result in a separate tab

Test name	Executions per second
Native findIndex	24206424.0 Ops/sec
_.findIndex	8466531.0 Ops/sec

Related benchmarks:

native findIndex vs lodash findIndex test (version: 0)

Compare performance of native [].findIndex and _.findIndex

Comparing performance of: Native findIndex vs _.findIndex

Created: one year ago by: Registered User

Jump to the latest result

Native findIndex

_.findIndex

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