zlacker

[return to "Firefox has surpassed Chrome on Speedometer"]
1. e4m2+p6[view] [source] 2023-07-18 12:43:48
>>akyuu+(OP)
See also https://arewefastyet.com.
◧◩
2. austin+MR[view] [source] 2023-07-18 15:37:18
>>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.

◧◩◪
3. kstrau+vn1[view] [source] 2023-07-18 17:27:24
>>austin+MR
How many cores was laptop benchmark running on?
◧◩◪◨
4. austin+fO1[view] [source] 2023-07-18 19:19:25
>>kstrau+vn1
I believe the CPU is 4 core, JavaScript is single threaded (multi-callstack) so you only get 1 logical CPU core.
◧◩◪◨⬒
5. kstrau+og2[view] [source] 2023-07-18 21:51:10
>>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?

◧◩◪◨⬒⬓
6. austin+0x2[view] [source] 2023-07-19 00:05:05
>>kstrau+og2
Appears to be: https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc

Its just a crude memory operation for Firefox. The video card in my laptop is super inferior compared to my desktop, so in most other benchmarks the laptop is much slower. The laptop has DDR4 memory where the desktop has slower DDR3 memory.

[go to top]