Single page Print


The usefulness of Javascript microbenchmarks for comparing browser performance may be on the wane, but these tests still allow us to tease out some single-threaded performance differences among CPUs. As part of our transition to using the Mechanical TuRk to benchmark our chips, we've had to switch to Google's Chrome browser so that we can automate these tests. Chrome does perform differently on these benchmarks than Microsoft Edge, our previous browser of choice, so it's vitally important not to cross-compare these results with older TR reviews.


The WebXPRT 3 benchmark is meant to simulate some realistic workloads one might encounter in web browsing. It's here primarily as a counterweight to the more synthetic microbenchmarking tools above.

WebXPRT isn't entirely single-threaded—it uses web workers to perform asynchronous execution of Javascript in some of its tests.