The microblog: 2022.06.15 09:21:26

2022.06.15 09:21:26 (1536972131799486464) from Daniel J. Bernstein, replying to "Ruben Kelevra (@RubenKelevra)" (1536970083435790336):

Your numbers seem to indicate that, on your 4-core machine, Firefox startup wasn't even managing to keep 2 cores active on average. Could this limited attention to Firefox startup optimization perhaps be a hint that most users aren't spending all day waiting for Firefox to start?

2022.06.15 09:27:50 (1536973742215028736) from Daniel J. Bernstein:

The code that users spend the most time waiting for has much bigger incentives to be vectorized and multithreaded, even though this limits the Turbo Boost speedup. I'd expect a claim of an "extreme system-wide performance impact" to be backed by numbers for common bottlenecks.


2022.06.15 08:51:40 (1536964640336494592) from "Ruben Kelevra (@RubenKelevra)":

I can measure it, if you like. But I really doubt that it would show equal numbers. Well webpage computations are mainly JIT compilation of the main JavaScript and painting of the webpage. Painting is done in the GPU as far as I know in Firefox these days.

2022.06.15 08:59:46 (1536966680441630720) from Daniel J. Bernstein, replying to "Ruben Kelevra (@RubenKelevra)" (1536964640336494592):

The claim at hand isn't that there's a measurable performance difference. The claim at hand is that there is an "an extreme system-wide performance impact".

2022.06.15 09:13:18 (1536970083435790336) from "Ruben Kelevra (@RubenKelevra)":

Well here you go: 50% slower to start Firefox, have it restore the sessions and load the first webpage and close again.