Benchmark: Immer vs Spread Reducer With Filled State (replace with same key and value)

HTML Preparation code:

<script src="https://cdn.jsdelivr.net/npm/immer@3.1.3/dist/immer.umd.min.js"></script>
<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.5/lodash.min.js'></script>

Script Preparation code:

function getItems(count) {
  let id = 1;
  return _.times(count, () => ({
    name: "city" + id++,
    visited: true
  }))
}


data = getItems(1000).reduce((acc, curr) => ({ ...acc, [curr.name]: curr.visited }), {})
action = { name: 'city1', visited: true };

Tests:

immer
const reducer = (state, curr) => { return immer.produce(state, draft => { draft[curr.name] = curr.visited }) }; reducer(data, action)
Mutate
const reducer = (draft, curr) => { draft[curr.name] = curr.visited; return draft; }; reducer(data, action)
Spread
const reducer = (draft, curr) => ({ ...draft, [curr.name]: curr.visited }); reducer(data, action)
immer pull up
const reducer = immer.produce((draft, curr) => { draft[curr.name] = curr.visited; }); reducer(data, action)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
immer
Mutate
Spread
immer pull up

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

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

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

Browser/OS: Chrome 93 on Windows

View result in a separate tab

Test name	Executions per second
immer	1097762.0 Ops/sec
Mutate	3007565.0 Ops/sec
Spread	469928.7 Ops/sec
immer pull up	765202.8 Ops/sec

Immer vs Spread Reducer With Filled State (replace with same key and value) (version: 0)

Comparing performance of: immer vs Mutate vs Spread vs immer pull up

Created: 4 years ago by: Guest

Jump to the latest result

immer

Mutate

Spread

immer pull up

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A