Benchmark: object spread vs immutable-js set

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/immutable/3.8.2/immutable.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/immutability-helper@2.7.0/index.min.js"></script>

Tests:

object spread
let obj = {}; for(i=0;i<100;i++){ const key = 'key'+i const value = 'value'+i obj = {...obj, [key]: {key, value}} }
immutable-js
let obj = Immutable.Map(); for(i=0;i<100;i++){ const key = 'key'+i const value = 'value'+i obj = obj.set(key, {key, value}) }

Historical Performance Data aggregated from 13 community runs

Desktop Results:

Chrome 13 runs

immutable-js

72K/s

object spread

8K/s

Fastest: immutable-js (9.2x faster)

View exact numbers

✓ immutable-js: 71,570 ops/sec
• object spread: 7,749 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 spread
immutable-js

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; rv:138.0) Gecko/20100101 Firefox/138.0

Browser/OS: Firefox 138 on Mac OS X 10.15

View result in a separate tab

immutable-js

30K/s

object spread

15K/s

View exact numbers

Test name	Executions per second
✓ immutable-js	30,284 Ops/sec
object spread	14,651 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's break down the provided benchmark and its components.

**Benchmark Overview**

MeasureThat.net is a platform where users can create and run JavaScript microbenchmarks to compare the performance of different approaches. The provided benchmark compares the performance of two methods:

1. Object spread (using the `...` operator)
2. Immutable-js set (using the `Immutable.Map` class from the immutable library)

**Library and Purpose**

The immutable library is a popular JavaScript library for functional programming, providing data structures and utilities to work with immutable data.

* In this benchmark, the `Immutable.Map` class is used as a container to store key-value pairs. The `set` method is used to add new entries to the map.
* The `immutability-helper` library (version 2.7.0) is used to provide utility functions for working with immutable data structures.

**Options Compared**

The benchmark compares the performance of two approaches:

1. **Object Spread**: This approach uses the `...` operator to spread an object, creating a new object with the updated properties. In this case, it's used to create a nested object by adding key-value pairs to an existing object.
2. **Immutable-js Set**: This approach uses the `Immutable.Map` class from the immutable library to store key-value pairs. The `set` method is used to add new entries to the map.

**Pros and Cons of Each Approach**

**Object Spread:**

Pros:

* Lightweight and efficient, as it only creates a new object reference.
* Easy to understand and implement for developers familiar with JavaScript objects.

Cons:

* May lead to slower performance due to the overhead of creating a new object.
* Can result in a large number of temporary objects being created during iteration.

**Immutable-js Set:**

Pros:

* Provides a more functional programming approach, which can be beneficial for parallelization and scalability.
* Reduces memory allocation overhead by reusing the same immutable map instance.

Cons:

* Requires importing an additional library (immutable.js).
* May have slower performance due to the overhead of working with immutable data structures.

**Special JS Features or Syntax**

None mentioned in this benchmark.

**Other Alternatives**

In addition to object spread and immutable-js set, other alternatives could include:

1. Using `Array.prototype.reduce()` instead of object spread.
2. Utilizing a library like Lodash or Ramda for functional programming.
3. Implementing a custom data structure using JavaScript's built-in `Map` class.

These alternatives may offer different trade-offs in terms of performance, readability, and maintainability, depending on the specific use case.

When choosing between object spread and immutable-js set, consider the following factors:

* Performance: If speed is critical, object spread might be a better choice due to its lightweight nature. However, this comes with the risk of creating temporary objects during iteration.
* Scalability: Immutable-js set provides a more functional programming approach, which can be beneficial for parallelization and scalability.
* Code readability: Object spread is often easier to understand and implement for developers familiar with JavaScript objects.

Ultimately, the choice between object spread and immutable-js set depends on the specific requirements of your project.

object spread vs immutable-js set (version: 0)

Comparing performance of: `object spread vs immutable-js`

Created: 8 years ago by: Guest

Go to the latest result

object spread

immutable-js

Historical Performance Data aggregated from 13 community runs

Desktop Results:

Chrome 13 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 spread vs immutable-js set (version: 0)

Comparing performance of: object spread vs immutable-js

Created: 8 years ago by: Guest

Go to the latest result

object spread

immutable-js

Historical Performance Data aggregated from 13 community runs

Desktop Results:

Chrome 13 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 spread vs immutable-js`