Learn back-end development by writing real code

Boot.dev Blog ยป Javascript ยป Which Method of Iteration in JavaScript Is Fastest?

Which Method of Iteration in JavaScript is Fastest?

By Lane Wagner on Nov 8, 2019

Curated backend podcasts, videos and articles. All free.

If you're looking to become a backend developer, or just stay up-to-date with the latest backend technologies and trends, you found the right place. Subscribe below to get a copy of our newsletter, The Boot.dev Beat, each month in your inbox. No spam, no sponsors, totally free.

There are many ways to traverse an array in Javascript. In this benchmark, we will look at five different ways and the pros and cons of each. Keep in mind that these benchmarks were run in a Chrome browser on Codepen.io. Results will vary by browser/interpreter.

For a working example of these benchmarks, take a look at this codepen. All benchmarks we ran on an array of 1,000,000,000 items.

1st: Vanilla JS - Backwards

for (let i = arr.length-1; i>=0; i--){}

~ 30 milliseconds

Going backwards is faster than going forward! At each iteration the loop checks against a constant 0 zero value instead of calling the array’s .length property. I highly recommend NOT putting this optimization into practice however, it’s weird and results in hard to understand code.

2nd: Vanilla JS - Forwards

for (let i = 0; i< arr.length; i++){}

~39 milliseconds

3rd: ES6 forEach()

arr.forEach(function(element) {});

~180 milliseconds

Slow but with a more convenient syntax, nothing surprising here.

4th: jQuery Each

$.each(arr, function( index, value ) {});

~225 milliseconds

Eeeeeew… jQuery. Convenient if you live in 2010. Very Slow.

Wildcard: For..Of ES6

for (const item of arr){}

First and second time running: 153 Milliseconds

Third+ times running : ~18 milliseconds

This is weird, and I’m not sure how to explain it. Maybe someone smarter than me can tweet me the answer @wagslane . The first two times running this after a fresh browser load are quite slow, but then it gets blazingly fast. I’m assuming there are some es6 optimizations under the hood that kick in.

Find a problem with this article?

Report an issue on GitHub