Toggle navigation
MeasureThat
.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
Remove array element, findIndex and splice vs filter
(version: 0)
Comparing performance of:
Splice vs Filter
Created:
5 years ago
by:
Guest
Go to the latest result
Tests:
Splice
const a = ["a", "b", "c", "d", "e"]; const indexToRemove = a.findIndex(i => i === "d"); const b = a.splice(indexToRemove, 1);
Filter
const a = ["a", "b", "c", "d", "e"]; const b = a.filter(item => item !== "d")
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
Splice
Filter
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
4 months ago
)
User agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:6.8) Goanna/20260301 PaleMoon/34.1.0
Browser/OS:
Pale Moon (Firefox Variant) 34 on Windows
View result in a separate tab
Embed
Embed Benchmark Result
<iframe src="https://measurethat.net/Embed?id=626994" width="100%" height="500px"></iframe>
Filter
26.1M/s
Splice
1.5M/s
View exact numbers
Test name
Executions per second
✓
Filter
26,139,738 Ops/sec
Splice
1,521,356 Ops/sec
Autogenerated LLM Summary
(model
llama3.2:3b
, generated one year ago):
The provided JSON represents a JavaScript microbenchmark on the MeasureThat.net website. The benchmark compares two approaches to remove an element from an array: using `splice` and using `filter`. **Approach 1: Using `splice`** This approach uses the `splice` method to remove the specified index in the array. The syntax is as follows: ``` const a = [\"a\", \"b\", \"c\", \"d\", \"e\"];\r\nconst indexToRemove = a.findIndex(i => i === \"d\");\r\nconst b = a.splice(indexToRemove, 1); ``` This approach has the following pros and cons: Pros: * `splice` is an array method that modifies the original array. * It can be more efficient than other approaches for large arrays. Cons: * It modifies the original array, which might not be desirable if the original array needs to be preserved. * It requires finding the index of the element to remove using `findIndex`, which can be slow for large arrays. **Approach 2: Using `filter`** This approach uses the `filter` method to create a new array with the elements that do not match the specified condition. The syntax is as follows: ``` const a = [\"a\", \"b\", \"c\", \"d\", \"e\"];\r\nconst b = a.filter(item => item !== \"d\"); ``` This approach has the following pros and cons: Pros: * It does not modify the original array, which can be useful if the original array needs to be preserved. * It is generally faster than using `splice` for large arrays. Cons: * It creates a new array with the filtered elements, which can use more memory. * It returns an empty array if no elements match the condition. **Other considerations** When choosing between these two approaches, consider the following factors: * Memory usage: If memory is a concern, using `filter` might be a better choice since it does not modify the original array and uses less memory. * Performance: For large arrays, `filter` is generally faster than `splice`. * Modifying the original array: If you need to preserve the original array, using `filter` is a safer choice. **Library used** In this benchmark, the `findIndex` method from the Array prototype object is used. The `findIndex` method returns the index of the first element that satisfies the provided testing function. **Special JS feature or syntax** The provided benchmark uses the following JavaScript features: * Arrow functions (`i => i === \"d\"`) * Template literals (`const a = [\"a\", ...]`) * String interpolation (`"item !== \"d\""`) These features are widely supported in modern JavaScript environments and do not require any special configurations or polyfills.
Related benchmarks
Remove by splice + findIndex vs filter
Lodash filter vs splice removing item from array
Deleting using .splice vs .filter
Remove by splice vs filter with a known index
Comments
Confirm delete:
Do you really want to delete benchmark?