Benchmark: object record find 100000

Script Preparation code:

var data = {};

var findId='data-id-999999';

// Generate more data
for (let i = 1; i <= 100000; i++) {
  var id = `data-id-${i}`;
  data[id] = { id: id };
}

Tests:

for...in loop
let result; for (const key in data) { if (data[key].id === findId) { result = data[key]; break; } }
Array.find
Object.values(data).find(item => item.id === findId);
for loop
const keys = Object.keys(data); for (let i = 0; i < keys.length; i++) { if (data[keys[i]].id === findId) { return data[keys[i]]; } }

Historical Performance Data aggregated from 6 community runs

Desktop Results:

Chrome 6 runs

for...in loop

62/s

for loop

62/s

Array.find

40/s

Fastest: for...in loop (1.6x faster)

View exact numbers

✓ for...in loop: 62 ops/sec
• for loop: 62 ops/sec
• Array.find: 40 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
for...in loop
Array.find
for loop

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 4 months ago)

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

Browser/OS: Chrome 146 on Windows

View result in a separate tab

for...in loop

71/s

for loop

70/s

Array.find

36/s

View exact numbers

Test name	Executions per second
✓ for...in loop	71 Ops/sec
for loop	70 Ops/sec
Array.find	36 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 provided JSON and benchmark test cases.

**Benchmark Test Cases**

The test cases are designed to measure the performance of three different approaches for finding an object with a specific property in JavaScript:

1. **For-in loop**: This approach uses the `for...in` loop to iterate over the properties of an object.
2. **Array.find**: This approach uses the `Array.prototype.find()` method to search for an element in an array.
3. **For loop (using Object.keys)**: This approach uses a traditional `for` loop with the `Object.keys()` method to get an array of property names, and then iterates over that array.

**Library Usage**

In this benchmark, the `Array.prototype.find()` method is used, which is a part of the ECMAScript standard. Specifically, it's implemented in V8 (the JavaScript engine used by Chrome) as `Array.prototype.find()`. This means that the test is specifically designed to measure the performance of this optimized implementation.

**Special JavaScript Features**

There are no special JavaScript features or syntaxes being tested here. The code snippets provided are straightforward and follow standard JavaScript conventions.

**Options Compared**

The three options being compared are:

* **For-in loop**: A legacy approach that uses `for...in` to iterate over object properties.
* **Array.find**: A modern approach that uses the optimized `Array.prototype.find()` method to search for an element in an array.
* **For loop (using Object.keys)**: A traditional approach that uses a `for` loop with the `Object.keys()` method to get an array of property names, and then iterates over that array.

**Pros and Cons**

Here are some pros and cons of each approach:

* **For-in loop**:
	+ Pros: Simple and easy to understand. Can be useful when working with legacy code or specific use cases.
	+ Cons: Slow performance compared to modern methods like `Array.find()`.
* **Array.find**:
	+ Pros: Fast performance, optimized implementation in V8, and widely supported across browsers and Node.js versions.
	+ Cons: May not work correctly if the input array is not sorted or if there are duplicate values.
* **For loop (using Object.keys)**:
	+ Pros: Can be useful when working with specific use cases that require a custom iteration approach.
	+ Cons: Slow performance compared to modern methods like `Array.find()` and may be less readable.

**Other Considerations**

When choosing an approach, consider the following factors:

* Performance requirements
* Code readability and maintainability
* Browser or Node.js version support
* Specific use case requirements

In general, if you need high performance and are working with modern JavaScript environments (e.g., Chrome, Node.js 14+), `Array.find()` is a good choice. For legacy code or specific use cases that require a custom iteration approach, the `For-in loop` or `For loop (using Object.keys)` may be more suitable.

If you're unsure about which approach to take, consider using the benchmark provided by MeasureThat.net as a reference point and experimenting with different approaches to determine the best fit for your specific use case.

object record find 100000 (version: 0)

Comparing performance of: `for...in loop vs Array.find vs for loop`

Created: one year ago by: Registered User

Go to the latest result

for...in loop

Array.find

for loop

Historical Performance Data aggregated from 6 community runs

Desktop Results:

Chrome 6 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

object record find 100000 (version: 0)

Comparing performance of: for...in loop vs Array.find vs for loop

Created: one year ago by: Registered User

Go to the latest result

for...in loop

Array.find

for loop

Historical Performance Data aggregated from 6 community runs

Desktop Results:

Chrome 6 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: `for...in loop vs Array.find vs for loop`