Thanks for sharing your interesting findings Daniel Reus !!! I appreciate you taking the time to leave such a thoughtful response.

Hopefully the great service JSPerf will be up soon; they broke a few months ago when ZEIT migrated to Vercel pending some configuration files that are being worked on in their GitHub repository here: https://github.com/jsperf/jsperf.com/issues/537 … There’s no reason it shouldn’t be up soon 😁

Looking at your results, you’re right that there’s a big difference in using console.log() vs. not doing so — thanks for investigating it and finding the factor of 800x slower, like you said.

Of course, even 60,000 operations per second with console.log() is massively fast, and a 1% difference (600 ops/sec) won’t make the least difference in a production app, I don’t think. It’s not like what I found for finding the minimum and maximum numbers in a JavaScript array.

The results from this particular article were from Firefox on Windows 7, 64-bit I believe.

When I do future performance testing, I’ll be sure to compare Firefox and Chrome, since JSPerf runs in your local browser. Firefox has the SpiderMonkey JavaScript engine, while Chrome has V8. Current versions of Edge run Chromium under the hood, so that’s V8 as well.

Thanks so much for sharing your findings! Cheers!!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store