Comment by vanderZwan

Comment by vanderZwan 11 days ago

You accidentally included the array initialization in the benchmarked code ("setup block" vs "boilerplate block"), dwarfing everything else. If we're talking about an already allocated array the difference is pretty big:

https://jsben.ch/FgDA6

… but in a way you're correct that this is rarely the actual bottleneck in the surrounding code. Still, "death by a thousand papercuts" and all that. Plus having old-school for-loops as a habit makes it easier to spot the true botllenecks.

akx 10 days ago

... derp, yes. It was way too early in the morning, and I misread "is part of the benchmark" as "is not part of the benchmark"...

Reply View 1 reply

vanderZwan 10 days ago

In your defense, the "use it for data initializing" suggestion isn't exactly helpful text either.
Also, for the record: I presume you tested on Chrome, but on Firefox the difference between the two loop styles is quite a bit larger (and generally slower than Chrome, so perhaps also a consideration when optimizing for "slowest browser" as the bottleneck).

Reply View | 0 replies