Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
creating new object vs changing fields
(version: 1)
perfomance differences
Comparing performance of:
new object vs mutate object
Created:
one year ago
by:
Guest
Jump to the latest result
Script Preparation code:
function throwErr() { throw new Error("message"); }
Tests:
new object
(function() { let result = {status: 200, message: "ok"}; try { throwErr(); } catch (error) { result = {status: 400, message: error.message}; } return result; })()
mutate object
(function() { const result = {status: 200, message: "ok"}; try { throwErr(); } catch (error) { result.status = 400; result.message = error.message; } return result; })()
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (2)
Previous results
Fork
Test case name
Result
new object
mutate object
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
one year ago
)
User agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Browser/OS:
Chrome 130 on Windows
View result in a separate tab
Embed
Embed Benchmark Result
Test name
Executions per second
new object
269840.7 Ops/sec
mutate object
271827.8 Ops/sec
Related benchmarks:
Return true vs empty body
Empty vs check
double bang vs typeof check
create object or create function
error handling: cost of try catch vs return (instanceof check vs prop check)
Spread vs Object.assign vs Object.create
Object.create(null) vs {} unknown property
Call or check
return err vs throw err
Comments
Confirm delete:
Do you really want to delete benchmark?