Which method is faster or more responsive in javascript, if-else, the ternary operator or logical OR? Which is advisable to use, for what reasons?
Seems like nobody did any actual profiling. Here's the code I used:
test = function() {
for (var i = 0; i < 10000000; i++) {
var a = i < 100 ? 1 : 2;
/*
if(i < 100) {
var a = 1;
}else{
var a = 2;
}
*/
}
}
test();
Using the if
/else
block instead of the ternary operator yields a 1.5 - 2x performance increase in Google Chrome v21 under OS X Snow Leopard.
As one use case where this is very important, synthesizing real-time audio is becoming more and more common with JavaScript. This type of performance difference is a big deal when an algorithm is running 44100 times a second.
I'm doing another syntax:
var a = true,
b;
b = (a == false)
? true // if a == false, b = true
: false; // else: a == true so b = false
/* Equivalent of
if(a == true)
var b = true;
else
var b = false;
Some people like my code and tell me it's simple to read.
I didn't think @charlie robert's test was fair
result:
normal equal and normal ternary slowest.
var a = true, b;
if (a === true) {
b = true;
} else {
b = false
}
if (a === false) {
b = true;
} else {
b = false;
}
var a = true, b;
b = (a === true) ? true : false;
b = (a === false) ? true : false;
var a = true, b;
if (a == true) {
b = true;
} else {
b = false;
}
if (a == false) {
b = true;
} else {
b = false;
}
var a = true, b;
b = (a == true) ? true : false;
b = (a == false) ? true : false;
var a = true, b;
if (a) {
b = true;
} else {
b = false;
}
if (!a) {
b = true;
} else {
b = false;
}
var a = true, b;
b = (a) ? true : false;
b = (!a) ? true : false;
Ternary operator is only syntactic sugar, not a performance booster.
to charlie roberts' answer above, I would add:
the following link gives some incisive answers; the result for switches in Firefox being the most striking: http://jsperf.com/if-else-vs-arrays-vs-switch-vs-ternary/39
Those who question why anyone would investigate optimization to this degree would do well to research WebGL!
The speed difference will be negligible - use whichever you find to be more readable. In other words I highly doubt that a bottleneck in your code will be due to using the wrong conditional construct.