Benchmark: Access property directly vs Getter/Setter

Script Preparation code:

class Foo {
	bar = {
      a: {
        val: 123
      }
    }

	get propAccessor() {
		return this.bar.a.val;
	}

	set propAccessor(val) {
		this.bar.a.val = val;
	}
}

var obj = new Foo();

Tests:

Read directly from prop
var value = obj.bar.a.val;
Set directly to prop
obj.bar.a.val = 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 year ago)

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

Browser/OS: Chrome 108 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Read directly from prop	27726220.0 Ops/sec
Set directly to prop	27070570.0 Ops/sec
Read from getter	27754450.0 Ops/sec
Set to setter	27174540.0 Ops/sec

Access property directly 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