CODEWITHSUNDEEP
javascriptperformanceprototype
mjey
mjey

Reputation: 183

Why is prototype function 40x slower than the default declared function?

I've played with jsperf.com and found that prototyped function is 40x slower than "default" declared function.

String.prototype.contains = function(s){ return !!~this.indexOf(s) } = 220K ops/s

vs.

function isContains(str, s) { return !!~str.indexOf(s) } = 8.5KK ops/s

Here's a jsperf test case

P.S. I know that prototype modification isn't the best case and can be named 'monkey patching' :)

Upvotes: 6

Views: 1196

Answers (2)

Dagg Nabbit
Dagg Nabbit

Reputation: 76786

I think it is slow because the string primitive is automatically wrapped with a temporary object each time a method is called.

This also explains the performance boost of new Object("hi").foo() over "hi".foo().

From the MDN docs:

String literals (denoted by double or single quotes) and strings returned from String calls in a non-constructor context (i.e., without using the new keyword) are primitive strings. JavaScript automatically converts primitives and String objects, so that it's possible to use String object methods for primitive strings. In contexts where a method is to be invoked on a primitive string or a property lookup occurs, JavaScript will automatically wrap the string primitive and call the method or perform the property lookup.

Nearby:

Why can't I add properties to a string object in javascript?

String object versus literal - modifying the prototype?

Upvotes: 6

Charlie Martin
Charlie Martin

Reputation: 112424

Odds are very good that you're replacing a primitive function implemented in C/machine code with a JavaScript body in the monkey-patched version.

Upvotes: 1

Related Questions