docs(benchmark): update benchmark data

README.md

@@ -110,7 +110,7 @@ Mutative is up to 6x faster than naive handcrafted reducer for updating immutabl
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.10 vs Immer v10.1.1]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.11 vs Immer v10.1.1]
 
 ![Benchmark](benchmark.jpg)
 

website/blog/releases/1.0/index.md

@@ -94,23 +94,23 @@ const state = create(baseState, (draft) => {
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.10 vs Immer v10.1.1]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.11 vs Immer v10.1.1]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,486 ops/sec ±0.85% (98 runs sampled)
-Mutative - No Freeze x 6,338 ops/sec ±1.14% (93 runs sampled)
-Immer - No Freeze x 5.32 ops/sec ±0.43% (18 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,469 ops/sec ±0.82% (99 runs sampled)
+Mutative - No Freeze x 6,015 ops/sec ±1.17% (94 runs sampled)
+Immer - No Freeze x 5.36 ops/sec ±0.28% (18 runs sampled)
 
-Mutative - Freeze x 969 ops/sec ±1.02% (98 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.44% (94 runs sampled)
+Mutative - Freeze x 959 ops/sec ±0.90% (99 runs sampled)
+Immer - Freeze x 382 ops/sec ±0.53% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 978 ops/sec ±0.22% (97 runs sampled)
-Immer - Patches and No Freeze x 5.32 ops/sec ±0.54% (18 runs sampled)
+Mutative - Patches and No Freeze x 970 ops/sec ±0.99% (96 runs sampled)
+Immer - Patches and No Freeze x 5.22 ops/sec ±0.80% (18 runs sampled)
 
-Mutative - Patches and Freeze x 507 ops/sec ±0.28% (97 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.76% (91 runs sampled)
+Mutative - Patches and Freeze x 505 ops/sec ±0.85% (93 runs sampled)
+Immer - Patches and Freeze x 275 ops/sec ±0.49% (89 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -121,7 +121,7 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,338 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,015 ops/sec`) and Immer (`382 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance).
 

website/docs/extra-topics/comparison-with-immer.md

@@ -25,23 +25,23 @@ Mutative has fewer bugs such as accidental draft escapes than Immer, [view detai
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.10 vs Immer v10.1.1]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.11 vs Immer v10.1.1]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,486 ops/sec ±0.85% (98 runs sampled)
-Mutative - No Freeze x 6,338 ops/sec ±1.14% (93 runs sampled)
-Immer - No Freeze x 5.32 ops/sec ±0.43% (18 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,469 ops/sec ±0.82% (99 runs sampled)
+Mutative - No Freeze x 6,015 ops/sec ±1.17% (94 runs sampled)
+Immer - No Freeze x 5.36 ops/sec ±0.28% (18 runs sampled)
 
-Mutative - Freeze x 969 ops/sec ±1.02% (98 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.44% (94 runs sampled)
+Mutative - Freeze x 959 ops/sec ±0.90% (99 runs sampled)
+Immer - Freeze x 382 ops/sec ±0.53% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 978 ops/sec ±0.22% (97 runs sampled)
-Immer - Patches and No Freeze x 5.32 ops/sec ±0.54% (18 runs sampled)
+Mutative - Patches and No Freeze x 970 ops/sec ±0.99% (96 runs sampled)
+Immer - Patches and No Freeze x 5.22 ops/sec ±0.80% (18 runs sampled)
 
-Mutative - Patches and Freeze x 507 ops/sec ±0.28% (97 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.76% (91 runs sampled)
+Mutative - Patches and Freeze x 505 ops/sec ±0.85% (93 runs sampled)
+Immer - Patches and Freeze x 275 ops/sec ±0.49% (89 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -52,7 +52,7 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,338 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,015 ops/sec`) and Immer (`382 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance). Run `yarn performance` to get all the performance results locally.
 

website/docs/getting-started/performance.md

@@ -82,23 +82,23 @@ const state = create(baseState, (draft) => {
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.10 vs Immer v10.1.1]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.11 vs Immer v10.1.1]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,486 ops/sec ±0.85% (98 runs sampled)
-Mutative - No Freeze x 6,338 ops/sec ±1.14% (93 runs sampled)
-Immer - No Freeze x 5.32 ops/sec ±0.43% (18 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,469 ops/sec ±0.82% (99 runs sampled)
+Mutative - No Freeze x 6,015 ops/sec ±1.17% (94 runs sampled)
+Immer - No Freeze x 5.36 ops/sec ±0.28% (18 runs sampled)
 
-Mutative - Freeze x 969 ops/sec ±1.02% (98 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.44% (94 runs sampled)
+Mutative - Freeze x 959 ops/sec ±0.90% (99 runs sampled)
+Immer - Freeze x 382 ops/sec ±0.53% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 978 ops/sec ±0.22% (97 runs sampled)
-Immer - Patches and No Freeze x 5.32 ops/sec ±0.54% (18 runs sampled)
+Mutative - Patches and No Freeze x 970 ops/sec ±0.99% (96 runs sampled)
+Immer - Patches and No Freeze x 5.22 ops/sec ±0.80% (18 runs sampled)
 
-Mutative - Patches and Freeze x 507 ops/sec ±0.28% (97 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.76% (91 runs sampled)
+Mutative - Patches and Freeze x 505 ops/sec ±0.85% (93 runs sampled)
+Immer - Patches and Freeze x 275 ops/sec ±0.49% (89 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -109,7 +109,7 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,338 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,015 ops/sec`) and Immer (`382 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance). Run `yarn performance` to get all the performance results locally.