(How the heck do categories and tags work???)
So I’ve seen a few tech publications mention compiling firefox (or chrome) as a benchmark. But I can’t seem to find any details about how this is done and how to reproduce it. In fact Wendell mentioned it in the threadripper review but it’s not part of any of the graphs in the video/article, and doesn’t seem to be a part of the open benchmarking suite (aside from some ancient thing no one uses). I think it’s mainly something LTT does, and to my knowledge, they don’t have the details of their benchmark stuff software wise documented anywhere.
Does anyone know of a standard, reproducible way to benchmark a firefox compile? I went off and followed the guides for doing the compile but it’s (understandably) set up in a way to be quick and easy to make and test code changes, which is to say a lot of stuff gets compiled once and then left in place, making re-running a bit of a chore.
I’ll go ahead and state I’m not really familiar with compiling code, I just think it’s an interesting test. So I might be missing obvious things.