3 ms·
Wow. As a non-expert about any of this technology, I must say that these comparisons are surprising. Maybe even too surprising. I wonder if maybe this could be
by bscphil 6y ago
Wow. As a non-expert about any of this technology, I must say that these comparisons are surprising. Maybe even too surprising. I wonder if maybe this could be the result of Firefox being built with different options for the nightly build than the release build. That might help explain the difference.
Then again, if I'm not mistaken I recall some messaging from Mozilla about Warp improving render time of heavy webapps without really helping the objective benchmarks. With such a consistent set of results it's hard to see how that could be the case (unless the benchmarks are once again behind the times), but I'm willing to give the benefit of the doubt on this. The worst case is, if it proves to be a regression, it'll probably get reverted. And Firefox as-is is already fast enough for my needs.
- slaymaker1907 6y agoMaybe they are optimizing stuff like compile times at the cost of throughout? My guess is that most JS code either doesn't need JIT at all or only needs the most minimal JIT and benchmarks tend to be bad at measuring those cases.