Benchmark: Proxy vs defineProperty

Script Preparation code:

object = { value: 'data', getData() {return this.value;} };
Object.defineProperty(object, 'dataProperty', {
  get() { return this.value; }
});
proxy = new Proxy(object, {})
proxyWithReflectHandler = new Proxy(object, {
	get(target, prop, receiver) {
    	return Reflect.get(target, prop, receiver)
    }
})
proxyWithHandler = new Proxy(object, {
	get(target, prop, receiver) {
    	return object[prop];
    }
})

Tests:

Object access
object.value;
Proxy access
proxy.value
Proxy with get handler access
proxyWithHandler.value
Use of simple getter
object.getData();
Use of defineProperty
object.dataProperty;
Proxy with get reflect handler access
proxyWithReflectHandler.value

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Object access
Proxy access
Proxy with get handler access
Use of simple getter
Use of defineProperty
Proxy with get reflect handler access

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 6 days ago)

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

Browser/OS: Chrome 135 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Object access	167017504.0 Ops/sec
Proxy access	60486272.0 Ops/sec
Proxy with get handler access	45591028.0 Ops/sec
Use of simple getter	174965376.0 Ops/sec
Use of defineProperty	175652096.0 Ops/sec
Proxy with get reflect handler access	33519834.0 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated 6 months ago):

LLMs can make mistakes. Check important info.

Let's dive into the world of JavaScript microbenchmarks!

**Benchmark Definition**

The provided JSON represents a benchmark that tests two approaches to accessing object properties: using the `.` operator (`object.value`) and using the `proxy` object with a proxy handler (`proxy.value`). The benchmark also tests using a simple getter function (`object.getData()`), using `defineProperty` to create a property on an object, and testing access through a custom proxy handler with both `get` handlers (`proxyWithReflectHandler` and `proxyWithHandler`).

**Options Compared**

The benchmark compares the following options:

1. **Direct Object Access**: Using the `.` operator to access an object property (`object.value`).
2. **Proxy Access**: Creating a proxy object (`proxy`) with no handler and accessing its properties through it (`proxy.value`).
3. **Simple Getter**: Using a getter function to provide access to an object's value (`object.getData()`).
4. **DefineProperty**: Creating a new property on an object using `defineProperty` and accessing it directly (`object.dataProperty`).
5. **Proxy with Reflect Handler**: Creating a custom proxy handler that uses the `Reflect.get` function to resolve property accesses, and accessing its properties through it (`proxyWithReflectHandler.value`).
6. **Proxy with Custom Handler**: Creating a custom proxy handler that simply returns the original value of an object's property when accessed, and accessing its properties through it (`proxyWithHandler.value`).

**Pros and Cons**

Here are some pros and cons of each approach:

* **Direct Object Access**:
	+ Pros: Simple, efficient, widely supported.
	+ Cons: Can lead to slower performance due to property lookups on objects.
* **Proxy Access**:
	+ Pros: Can improve performance by avoiding property lookups on objects, but may require more overhead for creating and managing proxies.
	+ Cons: Requires more code and configuration compared to direct object access.
* **Simple Getter**:
	+ Pros: Easy to implement and use, provides a clear separation of concerns between data storage and retrieval logic.
	+ Cons: May lead to slower performance due to function lookups.
* **DefineProperty**:
	+ Pros: Allows for more fine-grained control over property creation and access, can be used with other features like getters and setters.
	+ Cons: Requires more code and configuration compared to direct object access.
* **Proxy with Reflect Handler**:
	+ Pros: Provides a standardized way of handling property accesses, reduces the need for custom handler implementation.
	+ Cons: May require additional setup and configuration due to its reliance on the `Reflect` API.
* **Proxy with Custom Handler**:
	+ Pros: Provides flexibility in controlling how properties are accessed, allows for easy customization.
	+ Cons: Requires more code and configuration compared to direct object access or proxy access.

**Other Considerations**

When implementing these approaches, consider the following factors:

* Performance: Direct object access is generally faster than using a proxy or getter function. However, performance differences between proxies and getters can be significant depending on the specific use case.
* Code Complexity: Using a proxy handler requires more code and configuration compared to direct object access or simple getters.
* Maintenance and Debugging: Proxies with custom handlers may require more effort for maintenance and debugging due to their customization.

**Library Use**

The benchmark uses the `Proxy` API, which is a built-in JavaScript API that provides a way to create proxy objects. The `Reflect.get` function is used within the proxy handler to resolve property accesses.

**Special JS Features or Syntax**

This benchmark does not use any special JavaScript features or syntax beyond what's described in the benchmark definition.

Related benchmarks:

Proxy vs defineProperty (version: 0)

Comparing performance of: Object access vs Proxy access vs Proxy with get handler access vs Use of simple getter vs Use of defineProperty vs Proxy with get reflect handler access

Created: one year ago by: Guest

Jump to the latest result

Object access

Proxy access

Proxy with get handler access

Use of simple getter

Use of defineProperty

Proxy with get reflect handler access

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 6 months ago):