Tom Callaway <tcallawa@xxxxxxxxxx> writes: > Recently, someone filed a bug against chromium, noting that it was > benchmarking notably slower than Google Chrome or chromium-freeworld > (from rpmfusion). I tested locally and confirmed it. They suspected > that Fedora's optflags were to blame, but since chromium doesn't use > them anymore, that wasn't it. chromium-freeworld enables some media > codecs we cannot, but this shouldn't affect javascript benchmark > tests. VAAPI is turned on in both builds, but not in Google Chrome. > > Ultimately, the culprit was in how chromium is built for Fedora. There > are two ways to build chromium: as a giant static binary (which is how > Google Chrome and chromium-freeworld are built) and as a collection of > shared libraries (which is how Fedora's chromium is built). I did a > test build of a static version of Fedora's chromium and the benchmark > performance went up to expected levels. It's worth noting that IMHO, > the performance loss is noticeable, but the browser is still usable. > > So, you might be asking, why does Fedora build in shared mode? There are > two main reasons: > > 1) To enable users to be able to swap out the media components from > Fedora with a "freeworld" version. > > 2) To keep the size down on the chrome-remote-desktop subpackage > (since it can share the "internal libs" from chromium). > > Switching to static mode gives us: > > 1) Fully working krb5 (because it would resolve the symbol clash > caused by the use of chromium's boringssl fork). This bug has been > outstanding for a few years now. Biased of course, but this fix is really attractive to me. (For those who haven't experienced the issue, Kerberized browser login using FEDORAPROJECT.ORG is more likely to crash chromium than log in.) It sounds like from downthread that rpmfusion/freeworld isn't a concern anymore. That I think leaves chrome-remote-desktop, which doesn't seem a huge concern (but correct me if that's not right). So much as it pains me to suggest static linking, that would be my preference. Thanks, --Robbie
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
