Run results for: Better set.has vs array.includes

It often does not make sense to just compare only includes vs has. If we can not create the Set beforehand to be reused, and we need to initialize it every time, it will probably deteriorate the performance and we are better off using just simple include most of the times.

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 SberBrowser/13.0.7.0

Browser: Chrome 121

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: 2 years ago

includes

3.9M/s

lookup

615K/s

View exact numbers

Test name	Executions per second
✓ includes	3,932,468 Ops/sec
lookup	615,017 Ops/sec

Script Preparation code:

function generateRandomData(length) {
    const data = [];
    const characters = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789';

    for (let i = 0; i < length; i++) {
        let randomString = '';
        for (let j = 0; j < 20; j++) {
            randomString += characters.charAt(Math.floor(Math.random() * characters.length));
        }
        data.push({ value: randomString });
    }

    return data;
}

var data = generateRandomData(20);
var stringToBeChecked = data[15];

Tests:

includes
const a = data.map(x => x.value); return a.includes(stringToBeChecked);
lookup
const b = new Set(data.map(x => x.value)); return b.has(stringToBeChecked);