Benchmark: == null (with implicit conversion) vs (=== null || === undefined) vs util function

== null (with implicit conversion) vs (=== null || === undefined) vs util function (version: 1) Benchmark.js

Comparing performance of: `== null vs === null || === undefined vs == null (via util func) vs === null || === undefined (via util func) vs === null || === undefined || === "" vs === null || === undefined || === "" (via utility func) vs == null with complex object or array only vs == null with complex object or array only (via utility func)`

Created: 2 years ago by: Registered User

Go to the latest result

Script Preparation code:

var o = {abc:'Hello', prop2: 456, nested: {prop3: 'TheId'}};
var a = [[1,2,3],[36.664,53366]];
var u = undefined;
var n = null;
var d = 256.6353;
var f = NaN;
var b = true;
var s = 'a very long string 1233 all the way until the end';
//let m = new Symbol('ASymbol');
var l = false;
function i1(v) { return v == null; }
function i2(v) { return v === null || v === undefined; }
function i3(v) { return v === null || v === undefined || v === ''; }

Tests:

== null
if(o == null) l = true; if(a == null) l = true; if(u == null) l = true; if(n == null) l = true; if(d == null) l = true; if(f == null) l = true; if(b == null) l = true; if(s == null) l = true;
=== null || === undefined
if(o === null || o === undefined) l = true; if(a === null || a === undefined) l = true; if(u === null || u === undefined) l = true; if(n === null || n === undefined) l = true; if(d === null || d === undefined) l = true; if(f === null || f === undefined) l = true; if(b === null || b === undefined) l = true; if(s === null || s === undefined) l = true;
== null (via util func)
if(i1(o)) l = true; if(i1(a)) l = true; if(i1(u)) l = true; if(i1(n)) l = true; if(i1(d)) l = true; if(i1(f)) l = true; if(i1(b)) l = true; if(i1(s)) l = true;
=== null || === undefined (via util func)
if(i2(o)) l = true; if(i2(a)) l = true; if(i2(u)) l = true; if(i2(n)) l = true; if(i2(d)) l = true; if(i2(f)) l = true; if(i2(b)) l = true; if(i2(s)) l = true;
=== null || === undefined || === ""
if(o === null || o === undefined || o === '') l = true; if(a === null || a === undefined || a === '') l = true; if(u === null || u === undefined || u === '') l = true; if(n === null || n === undefined || n === '') l = true; if(d === null || d === undefined || d === '') l = true; if(f === null || f === undefined || f === '') l = true; if(b === null || b === undefined || b === '') l = true; if(s === null || s === undefined || s === '') l = true;
=== null || === undefined || === "" (via utility func)
if(i3(o)) l = true; if(i3(a)) l = true; if(i3(u)) l = true; if(i3(n)) l = true; if(i3(d)) l = true; if(i3(f)) l = true; if(i3(b)) l = true; if(i3(s)) l = true;
== null with complex object or array only
if(o == null) l = true; if(a == null) l = true; if(o == null) l = true; if(a == null) l = true; if(o == null) l = true; if(a == null) l = true; if(o == null) l = true; if(a == null) l = true;
== null with complex object or array only (via utility func)
if(i3(o)) l = true; if(i3(a)) l = true; if(i3(u)) l = true; if(i3(n)) l = true; if(i3(d)) l = true; if(i3(f)) l = true; if(i3(b)) l = true; if(i3(s)) l = true;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
== null
=== null \|\| === undefined
== null (via util func)
=== null \|\| === undefined (via util func)
=== null \|\| === undefined \|\| === ""
=== null \|\| === undefined \|\| === "" (via utility func)
== null with complex object or array only
== null with complex object or array only (via utility func)

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 2 years ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Browser/OS: Chrome 120 on Windows

View result in a separate tab

== null with complex object or array only

2.3M/s

== null

1.6M/s

== null (via util func)

950K/s

=== null || === undefined

582K/s

== null with complex object or array only (via utility func)

565K/s

=== null || === undefined || === "" (via utility func)

564K/s

=== null || === undefined (via util func)

563K/s

=== null || === undefined || === ""

490K/s

View exact numbers

Test name	Executions per second
✓ == null with complex object or array only	2,256,045 Ops/sec
== null	1,649,292 Ops/sec
== null (via util func)	949,545 Ops/sec
=== null \|\| === undefined	582,183 Ops/sec
== null with complex object or array only (via utility func)	564,580 Ops/sec
=== null \|\| === undefined \|\| === "" (via utility func)	564,379 Ops/sec
=== null \|\| === undefined (via util func)	563,454 Ops/sec
=== null \|\| === undefined \|\| === ""	489,681 Ops/sec

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

LLMs can make mistakes. Check important info.

It seems like you're sharing the results of some benchmarking tests for JavaScript comparison operators (`==`, `===`, etc.) in different scenarios, such as comparing null values with complex objects or arrays.

To summarize, here are the key takeaways:

1. **Comparison with null**: The most basic test, `== null`, tends to be the fastest among the options, often executing around 564-582 seconds per second (on a high-end machine).
2. **Null vs. undefined**: The comparison of null and undefined is slower than comparing null to any other value or object type, with times ranging from 582-630 seconds per second.
3. **Complex object/array comparisons**: When dealing with complex objects or arrays, the execution times can be significantly higher (often above 1000 seconds per second), especially when using `===` instead of `==`.
4. **Utility functions**: Using utility functions like `i3(o)` in the benchmarking test seems to slow down the execution times compared to simple equality checks.
5. **Multiple comparisons and logical operators**: The use of multiple comparisons (`&&`) and logical operators (`||`) can further increase the execution times, with some tests taking up to 1200 seconds per second.

Keep in mind that these results are specific to this particular benchmarking test suite and may not reflect real-world performance differences. Factors like JavaScript engine optimizations, system resources, and other external influences can impact actual usage scenarios.

Do you have any follow-up questions or would you like me to elaborate on any of these points?