Benchmark: Some vs Find - MeasureThat.net

Script Preparation code:

var data = []

for (let i = 0; i < 5000; ++i) data.push({ username: 'toto' })
data.push({ username: 'titi' })
for (let i = 0; i < 2500; ++i) data.push({ username: 'toto' })

Tests:

Find
data.find(e => e.username === 'titi')
Some
data.some(e => e.username === 'titi')

Historical Performance Data aggregated from 1,459 community runs

Desktop Results:

Chrome 1,222 runs

Find

151K/s

Some

151K/s

View exact numbers

✓ Find: 150,967 ops/sec
• Some: 150,751 ops/sec

Firefox 164 runs

Some

53K/s

Find

50K/s

View exact numbers

✓ Some: 52,629 ops/sec
• Find: 50,444 ops/sec

Safari 32 runs

Find

121K/s

Some

110K/s

View exact numbers

✓ Find: 120,904 ops/sec
• Some: 110,150 ops/sec

Other 6 runs

Some

138K/s

Find

126K/s

View exact numbers

✓ Some: 138,419 ops/sec
• Find: 125,907 ops/sec

Mobile Results:

Chrome 24 runs

Find

70K/s

Some

69K/s

View exact numbers

✓ Find: 70,081 ops/sec
• Some: 69,464 ops/sec

Safari 11 runs

Find

114K/s

Some

106K/s

View exact numbers

✓ Find: 113,711 ops/sec
• Some: 105,550 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
Some

Fastest: N/A

Slowest: N/A

Latest run results:

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

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0

Browser/OS: Firefox 140 on Linux

View result in a separate tab

Some

69K/s

Find

64K/s

View exact numbers

Test name	Executions per second
✓ Some	68,644 Ops/sec
Find	63,823 Ops/sec

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

LLMs can make mistakes. Check important info.

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

**Benchmark Definition**

The benchmark definition is a JSON object that specifies the script preparation code, HTML preparation code (which is empty in this case), and two test cases: "Find" and "Some".

**Script Preparation Code**

The script preparation code creates an array `data` with 5000 objects, each with a `username` property. The code then pushes 2500 more objects to the array, also with the same `username` property.

**Test Cases**

There are two test cases:

1. **Find**: This test case uses the `find()` method to search for an object in the `data` array that matches a condition: `e.username === 'titi'`. The `find()` method returns the first matching element or `undefined` if no match is found.
2. **Some**: This test case uses the `some()` method to check if at least one object in the `data` array meets the same condition: `e.username === 'titi'`. The `some()` method returns a boolean value indicating whether any element passed the test.

**Options Compared**

The two options being compared are:

* **Find**: This option uses the `find()` method, which is designed to return the first matching element in an array. It's typically used when you need to find a specific object in an array and use its properties.
* **Some**: This option uses the `some()` method, which checks if at least one element passes a test. It's typically used when you need to check if any elements in an array meet a condition.

**Pros and Cons**

Here are some pros and cons of each approach:

* **Find**:
	+ Pros: Efficient for finding a specific object in the array.
	+ Cons: May not be suitable for arrays where no elements match the test, as it returns `undefined`.
* **Some**:
	+ Pros: Suitable for arrays where you don't know if any elements will pass the test. It also works correctly with empty arrays.
	+ Cons: May be less efficient than `find()` in some cases, since it checks each element individually.

**Library and Purpose**

There is no library used in this benchmark definition. The `find()` and `some()` methods are built-in JavaScript methods.

**Special JS Feature or Syntax**

None of the test cases use any special JavaScript features or syntax beyond what's mentioned above.

Now, let's talk about other alternatives:

* **for...of` loop**: You could also write a `for...of` loop to iterate over the array and check each element for the condition. This approach would be more verbose than using `find()` or `some()`, but it's still a valid alternative.
* **Using a custom function**: Instead of using built-in methods like `find()` or `some()`, you could write a custom function to perform the same task. This approach would allow for more control over the implementation, but it might also be less efficient.

Keep in mind that benchmarking is often about measuring performance under different conditions, so the choice of approach will depend on the specific use case and requirements.

Some vs Find (version: 0)

Comparing performance of: `Find vs Some`

Created: 6 years ago by: Guest

Go to the latest result

Find

Some

Historical Performance Data aggregated from 1,459 community runs

Desktop Results:

Chrome 1,222 runs

Firefox 164 runs

Safari 32 runs

Other 6 runs

Mobile Results:

Chrome 24 runs

Safari 11 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Some vs Find (version: 0)

Comparing performance of: Find vs Some

Created: 6 years ago by: Guest

Go to the latest result

Find

Some

Historical Performance Data aggregated from 1,459 community runs

Desktop Results:

Chrome 1,222 runs

Firefox 164 runs

Safari 32 runs

Other 6 runs

Mobile Results:

Chrome 24 runs

Safari 11 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: `Find vs Some`