Why Is JavaScript Benchmarking a Mess?

JavaScript benchmarking is still necessary, especially as JavaScript is used in more performance-sensitive applications. JavaScript engines have been doing their best to mitigate timing attacks, along with a move to move to [Do Not Track] JavaScript engines intentionally make timing measurements inaccurate.

I hate benchmarking code, just like any human (which, at this point, most viewers of this probably aren’t ¯\(ツ)/¯). It is much more fun to pretend that your caching of a value increased performance by 1000% rather than testing to see what it did. Alas, benchmarking in JavaScript is still necessary, especially as JavaScript is used (when it shouldn’t be?) in more performance-sensitive applications. Unfortunately, due to many of its core architectural decisions, JavaScript doesn’t make benchmarking any easier.

What Is Wrong With JavaScript?

The JIT Compiler Cecreases Accuracy(?)

For those unfamiliar with the wizardry of modern ...