Benchmark: Is ternary operator, if-else or logical OR faster

Script Preparation code:

var a = true, b;

Tests:

strict equals
if (a === true) { b = true; } else { b = false } if (a === false) { b = true; } else { b = false; }
ternary strict equals
b = (a === true) ? true : false; b = (a === false) ? true : false;
simple equality
if (a == true) { b = true; } else { b = false; } if (a == false) { b = true; } else { b = false; }
simple ternary equality
b = (a == true) ? true : false; b = (a == false) ? true : false;
truthy / falsy
if (a) { b = true; } else { b = false; } if (!a) { b = true; } else { b = false; }
ternary truthy / falsy
b = (a) ? true : false; b = (!a) ? true : false;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
strict equals
ternary strict equals
simple equality
simple ternary equality
truthy / falsy
ternary truthy / falsy

Fastest: N/A

Slowest: N/A

Latest run results:

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

User agent: Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

Browser/OS: Chrome 126 on Chrome OS 14541.0.0

View result in a separate tab

ternary strict equals

1.8M/s

strict equals

1.7M/s

simple equality

1.7M/s

simple ternary equality

1.7M/s

truthy / falsy

1.6M/s

ternary truthy / falsy

1.6M/s

View exact numbers

Test name	Executions per second
✓ ternary strict equals	1,752,459 Ops/sec
strict equals	1,740,551 Ops/sec
simple equality	1,699,295 Ops/sec
simple ternary equality	1,665,967 Ops/sec
truthy / falsy	1,590,678 Ops/sec
ternary truthy / falsy	1,584,620 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

Let's break down what's being tested in the provided JSON benchmark.

**Benchmark Description**

The benchmark is designed to compare the performance of three different logical operators:

1. **Strict Equals (`===`)**
2. **Ternary Strict Equals (using `?:` operator)**
3. **Simple Equality (`==`)**
4. **Simple Ternary Equality (using `?:` operator)**
5. **Truthy/Falsy Checks (`if (condition)` vs `(!condition)`)**

These operators are used to check the values of variables `a` and `b`.

**Options Compared**

The benchmark compares the performance of each operator in two ways:

* In a single statement, where only one assignment is made.
* In a loop, where the same assignment is repeated multiple times.

**Pros and Cons of Each Approach**

1. **Strict Equals (`===`)**
	* Pros: More precise and reliable way to compare values.
	* Cons: Can be slower due to type checking and potentially more complex code path.
2. **Ternary Strict Equals (using `?:` operator)**
	* Pros: Similar performance to strict equals, but with the added convenience of a single expression.
	* Cons: May not be as readable or maintainable for some developers.
3. **Simple Equality (`==`)**
	* Pros: Faster and more concise way to compare values.
	* Cons: Less reliable than strict equals, as it can lead to unexpected behavior due to type coercion.

**Libraries and Special JS Features**

In the provided benchmark code, no specific libraries are used beyond the JavaScript language itself. However, some older browsers may require additional polyfills or workarounds to support modern features like `===`, `?:`, and `==`.

No special JavaScript features are mentioned in the benchmark definition.

**Other Considerations**

When writing benchmarks, it's essential to consider factors like:

* **Code readability**: Clear and concise code is often preferred over performance-critical optimizations.
* **Maintainability**: Benchmarks should be designed to be easy to understand and modify for future testing or updates.
* **Scalability**: The benchmark should be able to handle a range of inputs, data structures, and system configurations.

**Alternatives**

If you need to benchmark similar operators or expressions, consider exploring other options:

* For general-purpose benchmarking: SeeBench, JavaScriptPerf, or Benchmark.js
* For comparing specific operator performance: You can use the same JSON structure and create new benchmarks for different operators or scenarios.

Remember to carefully evaluate your benchmarking strategy and test cases to ensure accurate results.

Is ternary operator, if-else or logical OR faster (version: 0)

Comparing performance of: `strict equals vs ternary strict equals vs simple equality vs simple ternary equality vs truthy / falsy vs ternary truthy / falsy`

Created: 2 years ago by: Guest

Go to the latest result

strict equals

ternary strict equals

simple equality

simple ternary equality

truthy / falsy

ternary truthy / falsy

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Is ternary operator, if-else or logical OR faster (version: 0)

Comparing performance of: strict equals vs ternary strict equals vs simple equality vs simple ternary equality vs truthy / falsy vs ternary truthy / falsy

Created: 2 years ago by: Guest

Go to the latest result

strict equals

ternary strict equals

simple equality

simple ternary equality

truthy / falsy

ternary truthy / falsy

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `strict equals vs ternary strict equals vs simple equality vs simple ternary equality vs truthy / falsy vs ternary truthy / falsy`