Benchmark: Array HashMap comparison

Script Preparation code:

const long_text = "the the the the the Ladies others the six desire age. Bred am soon park past read by lain. As excuse eldest no moment. An delight beloved up garrets am cottage private. The far attachment discovered celebrated decisively surrounded for and. Sir new the particular frequently \
indulgence excellence how. Wishing an if he sixteen visited tedious subject it. Mind mrs yet did quit high even you went. Sex against the two however not nothing prudent colonel greater. Up husband removed parties staying he subject mr. \
Shot what able cold new the see hold. Friendly as an betrayed formerly he. Morning because as to society behaved moments. Put ladies design mrs sister was. Play on hill felt john no gate. Am passed figure to marked in. Prosperous middletons is ye inhabiting as \
assistance me especially. For looking two cousins regular amongst. \
Do commanded an shameless we disposing do. Indulgence ten remarkably nor are impression out. Power is lived means oh every in we quiet. Remainder provision an in intention. Saw supported too joy promotion engrossed propriety. Me till like it sure no sons. \
Impossible considered invitation him men instrument saw celebrated unpleasant. Put rest and must set kind next many near nay. He exquisite continued explained middleton am. Voice hours young woody has she think equal. Estate moment he at on wonder at season little. Six \
garden result summer set family esteem nay estate. End admiration mrs unreserved discovered comparison especially invitation. \
Friendship contrasted solicitude insipidity in introduced literature it. He seemed denote except as oppose do spring my. Between any may mention evening age shortly can ability regular. He shortly sixteen of colonel colonel evening cordial to. Although jointure an my \
of mistress servants am weddings. Age why the therefore education unfeeling for arranging. Above again money own scale maids ham least led. Returned settling produced strongly ecstatic use yourself way. Repulsive extremity enjoyment she perceived nor. \
Offices parties lasting outward nothing age few resolve. Impression to discretion understood to we interested he excellence. Him remarkably use projection collecting. Going about eat forty world has round miles. Attention affection at my preferred offending shameless \
me if agreeable. Life lain held calm and true neat she. Much feet each so went no from. Truth began maids linen an mr to after. \
At as in understood an remarkably solicitude. Mean them very seen she she. Use totally written the observe pressed justice. Instantly cordially far intention recommend estimable yet her his. Ladies stairs enough esteem add fat all enable. Needed its design number \
winter see. Oh be me sure wise sons no. Piqued ye of am spirit regret. Stimulated discretion impossible admiration in particular conviction up. \
Do play they miss give so up. Words to up style of since world. We leaf to snug on no need. Way own uncommonly travelling now acceptance bed compliment solicitude. Dissimilar admiration so terminated no in contrasted it. Advantages entreaties mr he apartments do. Limits far yet turned highly repair parish talked six. Draw fond rank form nor the day eat. \
Consulted he eagerness unfeeling deficient existence of. Calling nothing end fertile for venture way boy. Esteem spirit temper too say adieus who direct esteem. It esteems luckily mr or picture placing drawing no. Apartments frequently or motionless on reasonable projecting expression. Way mrs end gave tall walk fact bed. \
Is he staying arrival address earnest. To preference considered it themselves inquietude collecting estimating. View park for why gay knew face. Next than near to four so hand. Times so do he downs me would. Witty abode party her found quiet law. They door four bed fail now have. ";

const words = long_text.split(/\s+/);
var array = [];
var hashMap = {};
for (let word of words) {
  array.push(word);
  hashMap[word]= (hashMap[word] || 0) + 1;
}

Tests:

HashMap#in
const result = 'Impression' in hashMap;
HashMap#property
const result = hashMap.Impression;
HashMap#hasOwnProperty
const result = hashMap.hasOwnProperty('Impression');
Array#includes
const result = array.includes('Impression');
Array#indexOf
const result = array.indexOf('Impression') !== -1;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
HashMap#in
HashMap#property
HashMap#hasOwnProperty
Array#includes
Array#indexOf

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

**Benchmark Overview**

MeasureThat.net is a platform that allows users to create and run JavaScript microbenchmarks. The provided benchmark measures the performance of three data structures: arrays and hash maps.

**Benchmark Definition**

The benchmark defines four test cases:

1. `HashMap#in`: Tests if an object property exists in a hash map.
2. `HashMap#property`: Attempts to access a non-existent property on a hash map.
3. `HashMap#hasOwnProperty`: Checks if an object property belongs to the current object using `hasOwnProperty`.
4. `Array#includes` and `Array#indexOf`: Tests for membership of an element in an array.

**Options Compared**

The benchmark compares different approaches:

* `HashMap#in`:
	+ Using the `in` operator.
	+ Directly accessing a property (property access).
* `HashMap#property`:
	+ Accessing a non-existent property.
* `HashMap#hasOwnProperty`:
	+ Using the `hasOwnProperty` method.
* `Array#includes` and `Array#indexOf`:
	+ Using the `includes` method.
	+ The `indexOf` method with a negative index check.

**Performance Comparison**

The benchmark measures the performance of each test case, including:

* Browser: Opera 66
* DevicePlatform: Desktop
* OperatingSystem: Linux
* ExecutionsPerSecond: The number of executions per second for each test case

The results show that:

* `Array#includes` is the fastest method.
* `HashMap#hasOwnProperty` is faster than property access using `in`.
* Directly accessing a non-existent property (property access) in `HashMap#property` is slower than using `hasOwnProperty`.

**Implications**

These results suggest that when working with hash maps, it's generally faster to use the `hasOwnProperty` method or directly check for existence using the `in` operator instead of attempting to access a non-existent property. When working with arrays, using the `includes` method is likely the fastest approach.

Keep in mind that these results are specific to the test case and may not generalize to all scenarios. Additionally, performance can vary depending on the JavaScript engine, hardware, and other factors.

Latest run results:

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

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36 OPR/66.0.3515.44

Browser/OS: Opera 66 on Linux

View result in a separate tab

Test name	Executions per second
HashMap#in	11386199.0 Ops/sec
HashMap#property	12782343.0 Ops/sec
HashMap#hasOwnProperty	10857204.0 Ops/sec
Array#includes	14160824.0 Ops/sec
Array#indexOf	1793391.1 Ops/sec

Related benchmarks:

Array HashMap comparison (version: 2)

Comparing performance of: HashMap#in vs HashMap#property vs HashMap#hasOwnProperty vs Array#includes vs Array#indexOf

Created: 4 years ago by: Registered User

Jump to the latest result

HashMap#in

HashMap#property

HashMap#hasOwnProperty

Array#includes

Array#indexOf

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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