Benchmark: delete vs spread without vs spread override 2

Script Preparation code:

var query = {
    dates: [],
    latestDate: 'whatever'
};
var query2 = {
    current: {
        query: {
            dates: [1, 2, 3],
            latestDate: 'whatever2'
        }
    }
}

Tests:

delete
let storeQuery = { ...query }; let latestQuery = { ...query2.current?.query }; delete storeQuery.latestDate; delete latestQuery.latestDate;
spread without
const { latestDate: remove, ...storeQuery } = query; const { latestDate: remove1, ...latestQuery } = query2.current?.query || {};
spread override
const storeQuery = { ...query, latestDate: null }; const latestQuery = { ...query2.current?.query, latestDate: null };

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
delete
spread without
spread override

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

The provided JSON represents a JavaScript microbenchmark on MeasureThat.net, which tests the performance of different approaches for deleting properties from objects.

**Benchmark Description**

The benchmark is defined by a script and an HTML setup, but since it's not provided in the question, I'll explain the concept. Typically, this type of benchmark would test the time taken to delete specific properties or sets of properties from objects.

In this case, there are three individual test cases:

1. **delete**: This test case simply deletes the `latestDate` property from two separate objects: `storeQuery` and `latestQuery`.
2. **spread without**: This test case uses the spread operator (`{...query}`) to create a shallow copy of an object, but only removes the `latestDate` property from the resulting object.
3. **spread override**: Similar to the previous test case, this one creates a shallow copy of another object using the spread operator (`{...query2.current?.query}`), but also overrides any existing properties with new ones.

**Options Compared**

The three test cases compare different approaches to deleting properties:

* `delete`: Direct property deletion.
* `spread without`: Using the spread operator to create a shallow copy and then removing a specific property.
* `spread override`: Creating a shallow copy using the spread operator, overriding any existing properties with new ones.

**Pros and Cons**

Here are some pros and cons of each approach:

1. **delete**:
	* Pros: Simple and direct; likely to be faster since it doesn't involve creating a new object.
	* Cons: May cause unexpected behavior if the property is not properly defined or if there are side effects associated with deletion.
2. **spread without**:
	* Pros: Creates a safe copy of the original object, avoiding potential side effects from direct property deletion.
	* Cons: Requires more code and may be slower due to object creation.
3. **spread override**:
	* Pros: Combines the benefits of creating a new object with the safety of overriding existing properties.
	* Cons: May still have performance overhead due to object creation.

**Libraries and Special Features**

None of the test cases rely on specific libraries or syntax features, making them accessible to most JavaScript developers.

**Other Considerations**

When benchmarking property deletion in JavaScript, it's essential to consider:

* Object creation overhead
* Property access patterns (e.g., using `in` operator vs. bracket notation)
* Any side effects associated with property deletion (e.g., updating other properties or causing dependencies)

**Alternatives**

If you're looking for alternative approaches or want to explore different scenarios, you could consider the following:

* Using `Object.assign()` or a library like Lodash's `omit()` to create a new object without modifying the original.
* Exploring the performance impact of using `delete` vs. `splice()` to remove properties from an array-like object.
* Investigating the effects of using `Object.defineProperty()` or `Object.getOwnPropertyDescriptor()` for property access and manipulation.

Keep in mind that these alternatives may not be relevant to the specific use case or requirements of your project.

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 YaBrowser/23.3.3.709 Yowser/2.5 Safari/537.36

Browser/OS: Yandex Browser 23 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
delete	3326886.0 Ops/sec
spread without	7560072.5 Ops/sec
spread override	9877758.0 Ops/sec

Related benchmarks:

delete vs spread without vs spread override 2 (version: 0)

Comparing performance of: delete vs spread without vs spread override

Created: 2 years ago by: Guest

Jump to the latest result

delete

spread without

spread override

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):