MeasureThat.net

Run results for: Testing for false vs undefined vs == null vs hasOwnProperty vs hasOwn for undefined member

Is there a performance benefit to replacing == null with a logical test?

Go to the benchmark
Run details:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Chrome 130
Linux
Desktop
3 months ago
Test name Executions per second
test false 127937272.0 Ops/sec
test undefined 15704152.0 Ops/sec
test hasOwnProperty 95204312.0 Ops/sec
test == null 185662608.0 Ops/sec
test == undefined 15813345.0 Ops/sec
test static hasOwnProperty 7224817.0 Ops/sec
test static hasOwn 14250494.0 Ops/sec
Tests:

  • test false

    AخA
     
    var n = {};
    while(true) {
        if(!n.foo) 
            break;
    }

  • test undefined

     
    var n = {};
    while(true) {
        if(n.foo===undefined) 
            break;
    }

  • test hasOwnProperty

     
    var n = {};
    while(true) {
        if(!n.hasOwnProperty('foo')) 
            break;
    }

  • test == null

     
    var n = {};
    while(true) {
        if(n.foo==null) 
            break;
    }

  • test == undefined

     
    var n = {};
    while(true) {
        if(n.foo==undefined) 
            break;
    }

  • test static hasOwnProperty

     
    var n = {};
    while(true) {
        if(!Object.hasOwnProperty(n,'foo')) 
            break;
    }

  • test static hasOwn

     
    var n = {};
    while(true) {
        if(!Object.hasOwn(n, 'foo')) 
            break;
    }