3 ms·
If I modify that code to pre-initialise an array with the values 0 to N - 1, and then copy the value from that array to a new array (rather than using the loop
by nicoburns 8y ago
If I modify that code to pre-initialise an array with the values 0 to N - 1, and then copy the value from that array to a new array (rather than using the loop index), then both map and forEach are faster than the for loop for me.
- dahart 8y agoThat sounds fairly surprising, considering map has to allocate, and allocate is very expensive, but please share your code & I’ll try it. Like so? const N = 1000000 let a = new Array(N), b = new Array(N) for (let i = 0; i < N; i++) a[i] = i test('copy loop', _=> { for (var i = 0; i < N; i++) b[i] = a[i] }) test('copy map', _=> { b = a.map((x,i) => a[i]) }) test('copy forEach', _=> { a.forEach((v,i,a) => b[i] = a[i]) }) I get: copy loop 973, copy map 38, copy forEach 49. Same as before, but this time I tried Chrome in Windows. Are you using a different browser? I know that sometimes other browsers have very different results. In any case, it's somewhat irrelevant if there are cases that optimize and cases that don't. When idiomatic functional code is sometimes up to 30x slower than a for loop, it can't be used in perf critical sections. Even if it's only Chrome and only certain cases. The forEach perf needs to be always reliably performant before I can use it without worry.