[macOS] I ran this on macOS as well, and my results are more variable[1] there (not sure why), but the best score that I'm getting for Firefox there is 11.98 ± 0.19, vs. 8.923 ± 0.086 on Chrome. (higher is better) In those runs, Details|submetrics shows that we're spending 30.53ms in SelectingRange/Sync, whereas Chrome is spending 42.16ms in that submetric (lower is better). [1] In repeated reloads, I sometimes saw scores of ~8 or even ~6, but I did get 11 several times. No idea what's leading to the lower scores, but I suspect it's independent of the original issue that spawned this bug, which was a more "we're slower on-the-whole" issue, if I understand correctly.
Bug 1850834 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
[macOS] I ran this on macOS as well, and my results are more variable[1] there (not sure why), but the best score that I'm getting for Firefox there is 11.98 ± 0.19, vs. 8.923 ± 0.086 on Chrome. (higher is better) In those runs, Details|submetrics shows that we're spending 30.53ms in SelectingRange/Sync, whereas Chrome is spending 42.16ms in that submetric (lower is better). So it looks like we're winning there too. [1] In repeated reloads, I sometimes saw scores of ~8 or even ~6, but I did get 11 several times. No idea what's leading to the lower scores, but I suspect it's independent of the original issue that spawned this bug, which was a more "we're slower on-the-whole" issue, if I understand correctly.