Javascript; for vs forEach, which is faster in 2016?

Which of the cycles at the moment, js is faster for or foreach?

// Typical For loop
for(var i = 0; i < arrr.length; ++i) {
console.log(arrr[i].value);
i++;
}

// The same effect a forEach loop
arrr.forEach(function(arrr_item, i) {
console.log(arrr_item.value);
});


Online information for 2016 no. Judging by the fact that I'm somewhere long seen that forEach was/will gradually become faster for.
But, sobstvenno, the reason for the question: jsperf.com not available.

Thanks in advance for your help.
July 8th 19 at 12:11
4 answers
July 8th 19 at 12:13
Solution
jsperf.com unavailable

His counterpart is!
google.ru/search?q=javascript%20elapse%20milliseconds
I'm sorry, I didn't know... Thanks:) - Rick_Pfannersti commented on July 8th 19 at 12:16
If this was not possible, and jsperf.com would have been impossible. - mazie.Towne commented on July 8th 19 at 12:19
July 8th 19 at 12:15
Solution
In the engines where the forEach/map optimized speed is about the same as for, where there is no, for faster because a function call on each iteration further loading.
July 8th 19 at 12:17
Solution
Generally for faster, I think. Because forEach is a method. Call any function inhibits the interpreter. And if you have a very large array, the second will be called a huge number of functions.
So it is, but smart engines optimize it and put the code inline without call f-II - Rick_Pfannersti commented on July 8th 19 at 12:20
July 8th 19 at 12:19
Solution
Even for those who will measure speed possible useful knowledge about optimization of code by browsers and possible errors when measuring the speed of: https://www.youtube.com/watch?v=HPFARivHJRY

Find more questions by tags JavaScript