Toggle navigation
MeasureThat
.net
Create a benchmark
Tools
Feedback
Feature Requests
FAQ
Register
Log In
has vs find
(version: 0)
Benchmark.js
Comparing performance of:
find vs has
Created:
4 years ago
by:
Registered User
Go to the latest result
Tests:
find
const a = [1,2,3,4,5] a.find(x => x === 5);
has
const a = new Set([1,2,3,4,5]) a.has(5);
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
find
has
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
one year ago
)
User agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
Browser/OS:
Chrome 132 on Mac OS X 10.15.7
View result in a separate tab
Embed
Embed Benchmark Result
<iframe src="https://measurethat.net/Embed?id=582645" width="100%" height="500px"></iframe>
find
155.5M/s
has
21.9M/s
View exact numbers
Test name
Executions per second
✓
find
155,486,304 Ops/sec
has
21,862,550 Ops/sec
Autogenerated LLM Summary
(model
llama3.1:latest
, generated one year ago):
Let's dive into the explanation. **What is being tested?** The benchmark tests two different approaches to checking if an element exists in an array or a Set data structure: 1. **Using `find()` method**: In the first test case, it uses the `find()` method on an array `[1, 2, 3, 4, 5]` to find an element that matches a certain condition (`x === 5`). The benchmark measures how long it takes to run this operation. 2. **Using `has()` method**: In the second test case, it uses the `has()` method on a Set data structure created from an array `[1, 2, 3, 4, 5]` to check if an element exists (`a.has(5)`). The benchmark measures how long it takes to run this operation. **What are the options being compared?** The two test cases compare the performance of using `find()` on an array versus using `has()` on a Set data structure. Both methods aim to determine whether an element is present in the collection, but they use different approaches: * `find()` iterates through each element in the array until it finds one that matches the condition. * `has()` directly checks if the specified element exists in the Set. **Pros and Cons of each approach:** 1. **`find()` on an array:** * Pros: + Can be used with arrays, which are commonly used data structures. + Allows for more complex conditions to be checked (e.g., `x === 5 || x > 3`). * Cons: - Iterates through the entire array if the element is not found, which can be slower. 2. **`has()` on a Set:** * Pros: + Generally faster than `find()` for large datasets since it uses a hash-based lookup. - Allows for efficient checking of whether an element exists in the set. * Cons: - Only suitable for sets, which are created from arrays or other iterables. - May be less intuitive to use than `find()`. **Other considerations:** 1. **Data structure overhead:** While Sets are generally faster for lookup operations, creating a Set from an array can incur some overhead due to the additional memory allocation and hash computation involved. 2. **Cache behavior:** The performance difference between `find()` and `has()` might be influenced by cache behavior, especially in browsers where arrays and Sets may have different caching strategies. **Alternative approaches:** 1. **Using a more advanced data structure:** If you need to frequently check if an element exists while also iterating over the entire dataset (e.g., for logging or statistics), consider using a data structure that supports both operations efficiently, such as a combination of an array and an object. 2. **Implementing your own lookup function:** For specific use cases where performance is critical and you have control over the data structure, implementing a custom lookup function tailored to your needs might be more efficient than relying on built-in methods. **Library usage:** In this benchmark, no external libraries are used beyond the standard JavaScript `Array` and `Set` constructors.
Related benchmarks
set.has vs. array.find
#2 Array Includes vs. Find
Comments
Confirm delete:
Do you really want to delete benchmark?