Benchmark: Object.entries vs Object.keys vs for..in

Script Preparation code:

var obj = {
	a: 1,
    b: 2,
	c: 3,
	d: 4,
  	e: 7,
  	f: 3,
  	g: 14,
  	h: 1,
  	i: 88,
  	j: 0,
  	k: 5,
	0: 'a',
  	1: 'b',
  	str: 'long string',
	nested: {
    	nested: 0
    },
	hello: 55.5
};

Tests:

Object.entries
for (const [key, val] of Object.entries(obj)){ console.log(key, val); }
for..in
for (let key in obj) { console.log(key, obj[key]) }
Object.keys
for (let key of Object.keys(obj)) { console.log(key, obj[key]); }

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 runs

for..in

16K/s

Object.entries

15K/s

Object.keys

14K/s

Fastest: for..in (1.1x faster)

View exact numbers

✓ for..in: 16,362 ops/sec
• Object.entries: 14,994 ops/sec
• Object.keys: 14,348 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
Object.entries
for..in
Object.keys

Fastest: N/A

Slowest: N/A

Latest run results:

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

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

Browser/OS: Chrome 149 on Windows

View result in a separate tab

Object.entries

24K/s

for..in

23K/s

Object.keys

23K/s

View exact numbers

Test name	Executions per second
✓ Object.entries	23,869 Ops/sec
for..in	22,999 Ops/sec
Object.keys	22,660 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's break down what's being tested on MeasureThat.net:

**Benchmark Definition**

The website is testing three different approaches to iterate over an object in JavaScript:

1. **`for..in`**: This is a traditional method of iterating over an object's properties using the `for...in` loop.
2. **`Object.entries()`**: This is a modern method introduced in ECMAScript 2015 (ES6) that returns an array of a given object's key-value pairs, allowing for iteration using a simple `for...of` loop.
3. **`Object.keys()`**: This method returns an array of an object's own enumerable property names.

**Pros and Cons**

Here's a brief summary of the pros and cons of each approach:

* **`for..in`**:
	+ Pros: Wide support across older browsers, easy to understand for those familiar with traditional JavaScript.
	+ Cons: May not work as expected if an object has inherited properties from its prototype. Also, it returns both own enumerable and non-enumerable properties.
* **`Object.entries()`**:
	+ Pros: Modern method, works with modern browsers, and provides a clean and efficient way to iterate over key-value pairs.
	+ Cons: May not work in older browsers (pre-ES6), can be slower due to array operations.
* **`Object.keys()`**:
	+ Pros: Fast and efficient, works well in most modern browsers.
	+ Cons: Returns only enumerable properties, may not work if an object has non-enumerable properties.

**Other Considerations**

When choosing between these approaches, consider the following:

* If you need to support older browsers or require a more traditional iteration method, use `for..in`.
* For modern browsers and efficient key-value pair iteration, use `Object.entries()`. However, be aware that some older browsers may not support this method.
* When working with objects that have many properties, using `Object.keys()` might be faster due to the optimized lookup.

**Library/Functionality**

In the benchmark, we see that three functions are used:

1. **`Object.entries()`**: Returns an array of key-value pairs for a given object. Introduced in ECMAScript 2015 (ES6).
2. **`for...in`**: Iterates over an object's properties using the `for...in` loop.
3. **`Object.keys()`**: Returns an array of an object's own enumerable property names.

**Special JS Features/Syntax**

The benchmark uses modern JavaScript features, such as:

* **Arrow functions**: Used in the script preparation code (`var obj = {...} => { ... }`).
* **Template literals**: Used in the HTML preparation code (e.g., `"\r\n\t0: 'a',\r\n  \t1: 'b',\r\n"`).

However, there's no specific mention of special JavaScript features or syntax that are not present in the benchmark.

**Alternatives**

If you need to test other iteration methods or want to explore alternative approaches, consider:

* **`for...of`**: Similar to `Object.entries()`, but with a more traditional `for...loop` structure.
* **Using `Array.prototype.forEach()`**: Iterates over an array of values using the `forEach()` method.

Keep in mind that MeasureThat.net already tests these alternatives, so you can refer to their results for more information.

Object.entries vs Object.keys vs for..in (version: 0)

Comparing performance of: `Object.entries vs for..in vs Object.keys`

Created: 3 years ago by: Guest

Go to the latest result

Object.entries

for..in

Object.keys

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 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.entries vs Object.keys vs for..in (version: 0)

Comparing performance of: Object.entries vs for..in vs Object.keys

Created: 3 years ago by: Guest

Go to the latest result

Object.entries

for..in

Object.keys

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 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: `Object.entries vs for..in vs Object.keys`