Prototype vs Module pattern performance (v234)

Revision 234 of this benchmark created on

Description

Removed iterations in tests, because jsperf already does that for us. And renamed variables to be more meaningful to us humans. And other cosmetic changes.

The most important thing to remember is to use the right tool for the job. All these tests do is reference an object with a complex memory allocation. When you don't need something fancy, you're better off using a regular old object

Setup

function TraditionalPrototypeClass() {}
    
    TraditionalPrototypeClass.prototype.foo = function() {
      console.log(this);
    };
    
    TraditionalPrototypeClass.prototype.bar = function() {
      console.log(this);
    };
    
    function ModulePatternClass() {
      this.foo = function() {
        console.log(this);
      };
    
      this.bar = function() {
        console.log(this);
      };
    }
    
    var ModuleCachePatternClass = (function() {
      function foo() {
        console.log(this);
      }
    
      function bar() {
        console.log(this);
      }
    
      return function() {
        this.foo = foo;
        this.bar = bar;
      };
    }());
    
    var standardObject = {
      foo: function() {
        console.log(this);
      },
      bar: function() {
        console.log(this);
      }
    };

Test runner

Ready to run.

Testing in
TestOps/sec
Prototypal
var o = new TraditionalPrototypeClass()
o.bar;
o.foo;
ready
Module pattern
var o = new ModulePatternClass()
o.bar;
o.foo;
ready
Module pattern with cached functions
var o = new ModuleCachePatternClass()
o.bar;
o.foo;
ready
Use the right tool for the job
var o = standardObject;
o.bar;
o.foo;
ready

Revisions

You can edit these tests or add more tests to this page by appending /edit to the URL.