Benchmark: Direct access to property vs Getter/Setter

Script Preparation code:

class MyObj {
	prop = undefined

	get propAccessor() {
		return this.prop;
	}

	set propAccessor(val) {
		this.prop = val;
	}
}

var obj = new MyObj();

Tests:

Read directly from prop
var value = obj.prop;
Set directly to prop
obj.prop = 123;
Read from getter
var value = obj.propAccessor;
Set to setter
obj.propAccessor = 123;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Read directly from prop
Set directly to prop
Read from getter
Set to setter

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

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

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36

Browser/OS: Chrome 121 on Linux

View result in a separate tab

Test name	Executions per second
Read directly from prop	25907490.0 Ops/sec
Set directly to prop	25819460.0 Ops/sec
Read from getter	25126070.0 Ops/sec
Set to setter	25886030.0 Ops/sec

Direct access to property vs Getter/Setter (version: 0)

Comparing performance of: Read directly from prop vs Set directly to prop vs Read from getter vs Set to setter

Created: one year ago by: Registered User

Jump to the latest result

Read directly from prop

Set directly to prop

Read from getter

Set to setter

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A