Prototype vs Module pattern performance (v108)

Revision 108 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 () { return Math.random(); };
    
    TraditionalPrototypeClass.prototype.bar = function () { return Math.random(); };
    
    var standardObject = {
        foo: function () {
                return Math.random();
        },
        bar: function () {
                return Math.random();
        }
    };
    
    var moduleObject = (function () {
        return {
                foo: function () { return Math.random(); },
                bar: function () { return Math.random(); }
        };
    } ());
    
    var moduleCachedObject = (function () {
        function foo() { return Math.random(); }
    
        function bar() { return Math.random(); }
    
        return {
                foo: foo,
                bar: bar
        };
    } ());

Test runner

Ready to run.

Testing in
TestOps/sec
Prototypal
var o = new TraditionalPrototypeClass()
o.bar();
o.foo();
ready
Use the right tool for the job
var s = standardObject;
s.bar();
s.foo();
ready
moduleObject
var s = moduleObject;
s.bar();
s.foo();
ready
moduleCachedObject
var s = moduleCachedObject;
s.bar();
s.foo();
ready

Revisions

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