Benchmark: JS Find vs FindIndex

Script Preparation code:

var hasZero = [];
var withoutZero = [];
for (var i = 0; i < 10000; i++) {
  hasZero.push(Math.floor(Math.random() * 1000));
  withoutZero.push(Math.floor(Math.random() * 1000) + 1)
}

Tests:

Find
var tempResult = !!Math.round(Math.random()) ? hasZero.find(v => v === 0) : withoutZero.find(v => v === 0);
FindIndex
var tempResult = !!Math.round(Math.random()) ? hasZero.findIndex(v => v === 0) : withoutZero.findIndex(v => v === 0);

Historical Performance Data aggregated from 34 community runs

Desktop Results:

Chrome 22 runs

Find

222K/s

FindIndex

202K/s

View exact numbers

✓ Find: 221,536 ops/sec
• FindIndex: 202,473 ops/sec

Firefox 12 runs

FindIndex

39K/s

Find

39K/s

View exact numbers

✓ FindIndex: 39,216 ops/sec
• Find: 39,197 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
Find
FindIndex

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 15 days ago)

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

Browser/OS: Chrome 150 on Windows

View result in a separate tab

FindIndex

39K/s

Find

35K/s

View exact numbers

Test name	Executions per second
✓ FindIndex	38,638 Ops/sec
Find	35,168 Ops/sec

Autogenerated LLM Summary (model llama3.1:latest, generated one year ago):

LLMs can make mistakes. Check important info.

**Benchmark Overview**

The provided JSON represents a benchmark test case on MeasureThat.net, which compares the performance of two JavaScript methods: `find()` and `findIndex()`. These methods are used to search for an element in an array.

**What is being tested?**

In this benchmark, we have two test cases:

1. **Find**: This test uses the `find()` method to search for an element (`0`) in two separate arrays: `hasZero` and `withoutZero`. The `find()` method returns the first element that satisfies the provided condition (in this case, finding `0`).
2. **FindIndex**: Similar to the previous test, this uses the `findIndex()` method to search for an element (`0`) in both arrays. However, instead of returning the element itself, `findIndex()` returns its index.

**Library and Special JS Features/Syntax**

In this benchmark, there are no external libraries used. The only special JavaScript feature used is the arrow function syntax (`v => v === 0`), which is a concise way to define an anonymous function that takes one parameter (`v`) and returns `true` if it's equal to `0`, and `false` otherwise.

**Options Compared**

The two options being compared are:

1. **find()**: Returns the first element that satisfies the condition.
2. **findIndex()**: Returns the index of the first element that satisfies the condition, or `-1` if no such element exists.

**Pros/Cons of Different Approaches**

* `find()`:
	+ Pros: Easy to use and understand.
	+ Cons: If there are multiple elements satisfying the condition, it will return one of them. May not be desirable in some cases where a single result is not sufficient.
* `findIndex()`:
	+ Pros: Returns the index of the first matching element, making it easier to work with if you need to perform further operations on the array or its indices.
	+ Cons: More complex and less intuitive than `find()`. May require additional processing steps to extract the desired result.

**Other Considerations**

* Performance: The benchmark results show that `findIndex()` performs slightly better than `find()` in this specific scenario. However, the actual performance difference may vary depending on the size of the array, the complexity of the condition, and other factors.
* Code Readability: While `find()` is easier to read and understand, `findIndex()` requires a deeper understanding of how it works. In some cases, using `findIndex()` might be justified by its performance benefits, even if it makes the code slightly more complex.

**Other Alternatives**

In addition to `find()` and `findIndex()`, there are other methods you can use to search for elements in an array:

* **indexOf()**: Returns the index of the first occurrence of a specified value. Note that this method returns `-1` if the value is not found, unlike `findIndex()`.
* **filter()**: Creates a new array with all elements that satisfy the provided condition. This method is often used in conjunction with other methods to perform complex filtering and searching operations.
* **some()** and **every()**: These methods return `true` if at least one element (or every element) satisfies the condition, respectively. They can be useful when you need to check for the presence or absence of certain elements.

Keep in mind that each method has its own strengths and weaknesses, and the choice of which one to use depends on your specific requirements and the structure of your code.

JS Find vs FindIndex (version: 0)

Comparing performance of: `Find vs FindIndex`

Created: 6 years ago by: Guest

Go to the latest result

Find

FindIndex

Historical Performance Data aggregated from 34 community runs

Desktop Results:

Chrome 22 runs

Firefox 12 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.1:latest, generated one year ago):

JS Find vs FindIndex (version: 0)

Comparing performance of: Find vs FindIndex

Created: 6 years ago by: Guest

Go to the latest result

Find

FindIndex

Historical Performance Data aggregated from 34 community runs

Desktop Results:

Chrome 22 runs

Firefox 12 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.1:latest, generated one year ago):

Related benchmarks

Comparing performance of: `Find vs FindIndex`