zlacker

>>akyuu+(OP)
See also https://arewefastyet.com.

>>e4m2+p6
As a JavaScript developer my priorities are limited to visual render and DOM access. Going back 5+ years ago Chrome was able to access the DOM at about 45m ops/s on my desktop and Firefox was achieving about 850m ops/s on the same hardware. On my laptop (faster memory) Chrome was getting up to 55m ops/s while Firefox was around 1.4b ops/s.

Now Firefox numbers have remained constant, but Chrome struggles to hit 20m ops/s in my desktop. Chrome has sacrificed front end performance across the board for modest performance improvements to query string access of the DOM. Pretty unfortunate.

>>austin+MR
How many cores was laptop benchmark running on?

>>kstrau+vn1
I believe the CPU is 4 core, JavaScript is single threaded (multi-callstack) so you only get 1 logical CPU core.

>>austin+fO1
I thought so, but wasn't sure.

That makes me super suspicious of 1.4B op/s. Surely Firefox isn't accessing the DOM in ~2 CPU cycles?