Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
Public vs Private properties
(version: 1)
Comparing the get and set performance of directly accessing a field on a class versus using a getter/setter pair on a private property.
Comparing performance of:
Direct get vs proxied get vs direct set vs proxied set
Created:
one year ago
by:
Guest
Jump to the latest result
Script Preparation code:
class Test { get bar() { return this.#bar }; set bar(v) { this.#bar = v }; foo = 1; #bar = 1; } var test = new Test; var x;
Tests:
Direct get
x = test.foo;
proxied get
x = test.bar
direct set
test.foo = 2;
proxied set
test.bar = 2;
Rendered benchmark preparation results:
Suite status:
<idle, ready to run>
Run tests (4)
Previous results
Fork
Test case name
Result
Direct get
proxied get
direct set
proxied set
Fastest:
N/A
Slowest:
N/A
Latest run results:
Run details:
(Test run date:
one year ago
)
User agent:
Mozilla/5.0 (Android 15; Mobile; rv:137.0) Gecko/137.0 Firefox/137.0
Browser/OS:
Firefox Mobile 137 on Android
View result in a separate tab
Embed
Embed Benchmark Result
Test name
Executions per second
Direct get
553819520.0 Ops/sec
proxied get
562923328.0 Ops/sec
direct set
638606784.0 Ops/sec
proxied set
636245824.0 Ops/sec
Related benchmarks:
Ts trivial getter vs method
ES6 property (get/set) & getter/setter function & direct access to object attribute
ES6 property get & getter function & direct access to object attribute
Data Properties vs Getter / Setter Methods ES2015
Direct access to property vs Getter/Setter
Access property directly vs Getter/Setter
class set get (getters, function, direct)
Getter vs Direct Read
class getter/setter vs property
Comments
Confirm delete:
Do you really want to delete benchmark?