Get the latest tech news

JavaScript Benchmarking Is a Mess

Design decisions core to JavaScript have caused a multitude of problems for benchmarking. Is there a solution to this?

The 3 different commonly used JavaScript engines, V8, JSC, and SpiderMonkey for Chrome, Safari, and Firefox, respectively, all can perform significantly faster or slower on an equivalent piece of code. The garbage collector and its tendency to pause everything randomly The JIT compiler’s ability to delete to all of your code because it “isn’t necessary” Terribly broad flame graphs in most JavaScript devtools I think you get the point The most information you can get relating to runtime JavaScript performance in the browser will be from the Chrome devtools, which offer basic flame graph and CPU slowdown simulation utilities.

Get the Android app