I want to get more points in speedometer 3 using firefox. I’ve seen results above 20-24, but I can’t get more than 12 because js takes a long time to process. What to do? Rebuild firefox with the -0fast flag?? Or do something with config. I use some fixes in it which just extend limits for everything (almost)
Any suggestions are welcome
I’m guessing you’ve already happened across this, but in case you haven’t, here is an explanation of the the compilation flags thorium uses for it’s chromium builds:
https://thorium.rocks/optimizations
It seems as good of a place to start as any.
I haven’t spent a ton of time down this particular rabbit hole, but now I may have to.
@waz @soaska There are other reasons to be cautious about using AVX - older CPUs that support it are forcibly downclocked when the instructions are used so you’d better make sure that your vectorised loops are delivering enough benefits for the 10-20% penalty for all the rest of the code
https://stackoverflow.com/questions/56852812/simd-instructions-lowering-cpu-frequency
Ohh, cool. Thanks for the warning. This just got complicated enough that I am definitely going to have do go down this rabbit hole.
How are they using gcc and clang at the same time?
Interesting question. I don’t know. I haven’t actually had a chance to dig in yet.
Let me know if you find out pls
I realize what sub this is but really your best bet is probably to use a fork with optimized binaries (mercury comes to mind) it’s the best way to get fast firefox on arch too lol. the main repo package is fairly poor (on arch)
Immolo has a video on this subject https://yewtu.be/watch?v=umiVJdnZxMw
