Benchmark: find vs findIndex (Array prototype methods)

Script Preparation code:

var arr = [];
var i = 0;

while (i <= 1E5) arr[i] = i++;

Tests:

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

Historical Performance Data aggregated from 1,135 community runs

Desktop Results:

Chrome 924 runs

Array.prototype.find

2K/s

Array.prototype.findIndex

2K/s

View exact numbers

✓ Array.prototype.find: 2,064 ops/sec
• Array.prototype.findIndex: 2,056 ops/sec

Firefox 143 runs

Array.prototype.findIndex

3K/s

Array.prototype.find

3K/s

View exact numbers

✓ Array.prototype.findIndex: 2,782 ops/sec
• Array.prototype.find: 2,766 ops/sec

Safari 20 runs

Array.prototype.findIndex

16K/s

Array.prototype.find

15K/s

View exact numbers

✓ Array.prototype.findIndex: 15,622 ops/sec
• Array.prototype.find: 15,456 ops/sec

Other 16 runs

Array.prototype.findIndex

2K/s

Array.prototype.find

2K/s

View exact numbers

✓ Array.prototype.findIndex: 2,026 ops/sec
• Array.prototype.find: 1,926 ops/sec

Mobile Results:

Chrome 19 runs

Array.prototype.find

1K/s

Array.prototype.findIndex

999/s

View exact numbers

✓ Array.prototype.find: 1,044 ops/sec
• Array.prototype.findIndex: 999 ops/sec

Safari 13 runs

Array.prototype.find

17K/s

Array.prototype.findIndex

17K/s

View exact numbers

✓ Array.prototype.find: 16,705 ops/sec
• Array.prototype.findIndex: 16,652 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
Array.prototype.find
Array.prototype.findIndex

Fastest: N/A

Slowest: N/A

Latest run results:

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

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

Browser/OS: Opera 132 on Windows

View result in a separate tab

Array.prototype.findIndex

2K/s

Array.prototype.find

2K/s

View exact numbers

Test name	Executions per second
✓ Array.prototype.findIndex	2,269 Ops/sec
Array.prototype.find	2,265 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's dive into the benchmark and explore what's being tested.

**What is tested?**

The provided JSON represents two test cases: `Array.prototype.find` and `Array.prototype.findIndex`. Both tests are comparing the performance of these two methods on an array prototype, specifically when searching for a value equal to 1E5 (100,000).

**Options compared**

In this benchmark, only two approaches are being compared:

1. **Array.prototype.find**: This method returns the first element in the array that satisfies the provided condition (in this case, `item == 1E5`). If no such element exists, it returns undefined.
2. **Array.prototype.findIndex**: This method returns the index of the first element in the array that satisfies the provided condition (in this case, `item == 1E5`). If no such element exists, it returns -1.

**Pros and Cons of each approach**

Here's a brief summary:

* **Array.prototype.find**:
	+ Pros: More concise and expressive, as it directly returns the desired value.
	+ Cons: May be slower due to the overhead of searching for the first matching element.
* **Array.prototype.findIndex**:
	+ Pros: Faster, as it only needs to find the index of the first matching element, rather than the element itself.
	+ Cons: Returns an index, which might not be as intuitive or convenient in some cases.

**Library and purpose**

Neither `find` nor `findIndex` relies on any external libraries. They are both built-in methods of the JavaScript Array prototype.

**Special JS feature or syntax**

None mentioned explicitly, but keep in mind that modern JavaScript engines often optimize these methods for performance.

**Other alternatives**

If you wanted to test alternative approaches, you might consider:

* Using a custom loop or function to achieve the same result (e.g., `arr.forEach` or a simple iteration).
* Utilizing other array methods like `some`, `every`, or `includes`.
* Implementing a custom binary search algorithm for finding an element in the array.

However, these alternatives would not be directly comparable to the built-in `find` and `findIndex` methods, as they would likely have different performance characteristics and use cases.

find vs findIndex (Array prototype methods) (version: 0)

Measuring which is faster

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

Created: 7 years ago by: Registered User

Go to the latest result

Array.prototype.find

Array.prototype.findIndex

Historical Performance Data aggregated from 1,135 community runs

Desktop Results:

Chrome 924 runs

Firefox 143 runs

Safari 20 runs

Other 16 runs

Mobile Results:

Chrome 19 runs

Safari 13 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

find vs findIndex (Array prototype methods) (version: 0)

Measuring which is faster

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

Created: 7 years ago by: Registered User

Go to the latest result

Array.prototype.find

Array.prototype.findIndex

Historical Performance Data aggregated from 1,135 community runs

Desktop Results:

Chrome 924 runs

Firefox 143 runs

Safari 20 runs

Other 16 runs

Mobile Results:

Chrome 19 runs

Safari 13 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: `Array.prototype.find vs Array.prototype.findIndex`