@Desistance While that's always welcome to have at least parity with the fast competition, I never felt Firefox to be slower than Chromium based browsers. At least on my PC. Synthetic benchmarks are always that, just synthetic tests.
To be perfectly honest, you could just be less sensitive to it, or you're running on a machine that can brute force through it. Until very recently, Firefox was visibly under-performing compared to Chrome, especially for WebGL related tasks or when running on low powered laptops and mobile devices like my Surface Pro 7.
It's been improving a lot recently though, so much so that I've switched back from Brave to Firefox, but to say that benchmarks are just synthetic tests is being dismissive about Firefox's performance issues. Benchmarks are the only way to quantifiably and scientifically measure performance improvements and regressions. Simply using a browser and declaring whether its fast or slow is inaccurate at best and misleading at worse, and what's okay performance wise for you may not be okay for others.
It also depends highly on your browsing habits. If you're just reading news articles and watching videos, sure you probably won't notice the improvements that these benchmarks show. Nowadays, however, more and more sites are becoming full on applications that are doing way more Javascript operations in the background than a simple document and that's where these benchmark improvements really have an affect on everyday browsing.
Benchmarks are the only way to quantifiably and scientifically measure performance improvements and regressions.
I disagree with that. While your statement is correct in the sense you layed it out, it is not what I was saying. I am saying that benchmarks are testing what the benchmark is testing, not what the actual web usage of an individual is. And I am just speaking from my experience. Benchmarks do not represent reality. In example people have different configurations and addons, which has a huge impact on performance. Synthetic Benchmarks are often done with default configurations. I am not saying the results are wrong, they just don't hit the reality (sometimes they do).
EDIT: Does anyone know why there's that spike for most of the benchmarks starting February 8th/10th? Seems like it affected both Chrome/Chromium and Firefox, although in some cases FF seems to have been hit the most. A Kernel update maybe? Some syscall changed?
Could be a readjustment in the metrics. They fix test and measurement errors from time to time and it often looks like a spike. They attach notes to the data points sometimes. Maybe clicking one of them during that time will shed some light.
very nice but for me 115 has been a disaster, progressively using abnormally high amounts of RAM.
I'm just about done with this browser as a daily driver. will keep it as a backup. its always the same with firefox a few versions it runs great then comes another update that breaks the hell out of it.