Language Selection

English French German Italian Portuguese Spanish

Red Hat Enterprise Linux 8.0 Benchmarks Against RHEL 7.6, Ubuntu 18.04.2 LTS, Clear Linux

Filed under
Graphics/Benchmarks

Continuing on from the initial Red Hat Enterprise Linux 8.0 benchmarks last week, now having had more time with this fresh enterprise Linux distribution, here are additional benchmarks on two Intel Xeon servers when benchmarking RHEL 8.0, RHEL 7.6, Ubuntu 18.04.2 LTS, and Clear Linux. RHEL 8.0 is certainly delivering much better out-of-the-box performance than its aging predecessor but how can it compete with Ubuntu LTS and Clear Linux?

As a reminder as to what is shipped by each of these Linux distributions, the core components include:

Red Hat Enterprise Linux 7.6 - RHEL 7.6 uses a (heavily patched) Linux 3.10 kernel, GCC 4.8.5 compiler, and XFS file-system by default.

Red Hat Enterprise Linux 8.0 - RHEL 8.0 runs with the Linux 4.18 kernel, GCC 8.2.1 compiler, and XFS file-system by default. There is a slew of updated packages compared to RHEL7 and what's available there, including other changes like changing over to Retpolines for the Spectre V2 mitigations.

Read more

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights