Originally posted by skeevy420
View Post
Announcement
Collapse
No announcement yet.
Chrome 91 Benchmarks On Linux Showing Off Even Better Performance
Collapse
X
-
Originally posted by ZFKerr View PostChrome don't works on Wayland natively, but Firefox works. Chrome Wayland support currently work-in-progress, but only with Ozone abstraction layer, that by the way have dozens of issues, during Firefox works on Wayland full natively and I don't see any issues. On benchmarks Chrome works about 2x faster, but on practice I don't see it during every day web browsing. I used Chrome during many years, but switched to Firefox for native Wayland support.
You are right that in real-world usage, the performance difference hardly ever matters.
- Likes 3
Leave a comment:
-
Originally posted by Pajn View PostSparkplug should not make much of a difference in benchmarks as those mostly always should advance to Turbofan quite quickly, the big difference will be in actual websites that does not run the same JavaScript over and over and is similar to Firefoxs baseline compiler. When measuring browsers it's important to remember that they have very different performance characteristics over different workloads and that JavaScript heavy benchmarks have very little in common with normal browsing.
The more silly excuses that people make for firefox, the slower it will be.
The one component that Firefox excels with generally, is their brand new CSS system, but the Chrome developers would never argue that top line stylesheet performance doesn't matter, they would think about how to match it instead.
- Likes 5
Leave a comment:
-
Originally posted by skeevy420 View Post
I don't know why you'd think my cat Spark Plug would help in Chrome benchmarks either. He's much better with compression.
- Likes 9
Leave a comment:
-
Originally posted by discordian View Post"saves over 17 years of CPU time daily"
Yeah, and at the same time you lose millennia while decoding videos on those CPUs. Any crappy PC or even portables like the PSP could decode YouTube on hardware back in early 2000s, then came google and changed codecs to some crappy vp8, and on Linux hw decoding with chrome(ium) still doesn't work at all.
- Likes 3
Leave a comment:
-
"saves over 17 years of CPU time daily"
Yeah, and at the same time you lose millennia while decoding videos on those CPUs. Any crappy PC or even portables like the PSP could decode YouTube on hardware back in early 2000s, then came google and changed codecs to some crappy vp8, and on Linux hw decoding with chrome(ium) still doesn't work at all.
- Likes 7
Leave a comment:
-
Originally posted by Pajn View PostSparkplug should not make much of a difference in benchmarks as those mostly always should advance to Turbofan quite quickly, the big difference will be in actual websites that does not run the same JavaScript over and over and is similar to Firefoxs baseline compiler. When measuring browsers it's important to remember that they have very different performance characteristics over different workloads and that JavaScript heavy benchmarks have very little in common with normal browsing.
- Likes 15
Leave a comment:
-
Chrome don't works on Wayland natively, but Firefox works. Chrome Wayland support currently work-in-progress, but only with Ozone abstraction layer, that by the way have dozens of issues, during Firefox works on Wayland full natively and I don't see any issues. On benchmarks Chrome works about 2x faster, but on practice I don't see it during every day web browsing. I used Chrome during many years, but switched to Firefox for native Wayland support.Last edited by ZFKerr; 28 May 2021, 10:25 AM.
- Likes 17
Leave a comment:
Leave a comment: