Run results for: Array.find vs. Set.has

Run details:

User agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Mobile Safari/537.36

Browser: Chrome Mobile 144

Operating system: Android

Device Platform: Mobile

Date tested: 7 months ago

Benchmark engine: Benchmark.js

Set.has non-Existing

47.9M/s

Set.has existing

45.3M/s

Array.find existing

30.0M/s

Array.find non-existing

24.7M/s

View exact numbers

Test name	Executions per second
✓ Set.has non-Existing	47,869,588 Ops/sec
Set.has existing	45,339,616 Ops/sec
Array.find existing	30,043,012 Ops/sec
Array.find non-existing	24,686,876 Ops/sec

Script Preparation code:

const SOURCE_DATA = ['one', 'two', 'three', 'four', 'five', 'six'];
const arr = Array.from(SOURCE_DATA);
const set = new Set(SOURCE_DATA);
const existingItem = 'three';
const nonExistingItem = 'nine';
window.testData = {
  SOURCE_DATA,
  arr,
  set,
  existingItem,
  nonExistingItem
};

Tests:

Array.find existing
window.testData.arr.find(e => e === window.testData.existingItem);
Array.find non-existing
window.testData.arr.find(e => e === window.testData.nonExistingItem);
Set.has existing
window.testData.set.has(window.testData.existingItem)
Set.has non-Existing
window.testData.set.has(window.testData.nonExistingItem)

Run results for: Array.find vs. Set.has

Compares a performance of Array.find on a small number of items

Array.find existing

Array.find non-existing

Set.has existing

Set.has non-Existing