Sure, but that's expected because ARM essentially has hardware JavaScript acceleration built-in via FJCVTZS[0]. I personally don't find JavaScript specific benchmarks to be a good indicator of general computing power. (Ultimately, I spend little time in a web browser.)

FWIW, Cinebench multi-core benchmark is around 20% faster for me on the M1.

[0]: https://developer.arm.com/documentation/100076/0100/a64-inst...

> I personally don't find JavaScript specific benchmarks to be a good indicator of general computing power.

Many of us spend substantial periods of time writing up the technical documentation in Confluence or use JIRA. Confluence alone loads approximately 22Mb of mangled and compacted JavaScript for each open page in a separate browser tab.

Before M1, Confluence and JIRA were the single most source of a sustained battery drain, irrespective of the browser. On M1 based laptops, the battery impact is so negligible that it can be considered non-existent. How much of this subjected experience can be attributed just to the the ARM 8.3 JavaScript hardware acceleration is an interesting question as the JavaScript browser performance on Intel CPU's has also been affected by Spectre and Meltdown mitigations in the CPU microcode.

I doubt that instruction is relevant. It comes down to an abundance of microarchitectural resources on the M1. A 12th-gen Intel CPU gets 310 on this benchmark while having no particular accelerators. They just added tons of caches and buffers, like the M1 has.