Run results for: filter-map vs reduce fixed vs for

modified version of `map-filter vs reduce` that switches the order of operations Original was not fair comparison as it mapped all iterations not just the ones that passed the filter * added for loop

Go to the benchmark

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:132.0) Gecko/20100101 Firefox/132.0

Browser: Firefox 132

Operating system: Mac OS X 10.15

Device Platform: Desktop

Date tested: 22 days ago

Test name	Executions per second
map-filter	229317.9 Ops/sec
reduce	386619.7 Ops/sec
for	397900.7 Ops/sec

Script Preparation code:

a=[];
for(i=0;i<1000;i++) a.push(Number(i)/1000);
var filtering=x=>(x*114514)%1>0.5;
var mapping=x=>x+0.1919;
var reducing=(acc,x)=>{
  if((x*114514)%1>0.5) acc.push(x+0.1919);
  return acc;
}

const forLoop = (a) => {
  let acc = []
  for (let i = 0; i < a.length; i++) {
    let x = a[i];
    if ((x * 114514) % 1 > 0.5) acc.push(x + 0.1919);
  }
  return acc
}

Tests:

map-filter
a.filter(filtering).map(mapping);
reduce
a.reduce(reducing,[]);
for
forLoop(a)