Benchmark: Find vs FindIndex with object arrays

Script Preparation code:

var arr = [];
var i = 0;

while (i <= 1E5) arr[i] = { id: i++, date: Number(new Date()) };

Tests:

Array.prototype.find
const item = arr.find(item => item.id == 1E5);
Array.prototype.findIndex
const index = arr.findIndex(item => item.id == 1E5);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Array.prototype.find
Array.prototype.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.

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

**What is being tested?**

The provided JSON represents a JavaScript microbenchmark that compares the performance of two methods: `Array.prototype.find()` and `Array.prototype.findIndex()`. Both methods are used to search for an element with a specific property in an array.

**Options compared:**

1. `find()`: This method returns the first element in the array that satisfies the provided condition. If no element matches, it returns `undefined`.
2. `findIndex()`: This method returns the index of the first element in the array that satisfies the provided condition. If no element matches, it returns `-1`.

**Pros and Cons:**

* `find()` is generally faster than `findIndex()` because it doesn't require searching for an index, which can be slower.
* However, `findIndex()` provides more information about the search result (the actual value at the found index), whereas `find()` only returns a value if one exists.

**Library usage:**

In this benchmark, no libraries are explicitly mentioned. Both methods (`find()` and `findIndex()`) are built-in methods of the JavaScript Array prototype.

**Special JS features or syntax:**

* The benchmark uses the shorthand arrow function syntax (`item => item.id == 1E5`) to define the search condition.
* It also uses template literals (`Number(new Date())`) to create a date object as part of the array elements.

**Other considerations:**

* The benchmark creates an array with a large number of elements (100,000) to simulate real-world scenarios where performance is critical.
* The script preparation code uses a `while` loop to populate the array with elements, which can affect the overall performance of the benchmark.

**Alternatives:**

There are other methods that could be used to search for an element in an array, such as:

1. `forEach()`: This method executes the provided function on each element of the array.
2. `some()`: This method returns `true` if at least one element in the array satisfies the provided condition.
3. `every()`: This method returns `true` if all elements in the array satisfy the provided condition.

However, these methods are not as efficient as `find()` and `findIndex()` for searching a single value in an array.

In summary, this benchmark compares the performance of two built-in JavaScript methods (`Array.prototype.find()` and `Array.prototype.findIndex()`) that provide different results based on whether the search is successful or not. The pros and cons of each method are discussed, along with library usage and special syntax features used in the benchmark.

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/96.0.4664.45 Safari/537.36

Browser/OS: Chrome 96 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Array.prototype.find	663.4 Ops/sec
Array.prototype.findIndex	685.2 Ops/sec

Related benchmarks:

Find vs FindIndex with object arrays (version: 0)

Comparing performance of: Array.prototype.find vs Array.prototype.findIndex

Created: 3 years ago by: Guest

Jump to the latest result

Array.prototype.find

Array.prototype.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):