Fedora Linux Rawhide kernel performance is extremely poor due to too many debug options
2 min readFedora Linux Rawhide kernel performance is extremely poor due to too many debug options
- An American company made 0.7nm chips: EUV lithography machines can’t do it
- CVE-2007-4559 Python vulnerability ignored for 15 years puts 350,000 projects at risk of code execution
- RISC-V only takes 12 years to achieve the milestone of 10 billion cores
- 14000 cores + 450W: RTX 4080 graphics card perfectly replaces the RTX 3080
- Big upgrade: The difference between Bluetooth 5.0 and 5.2
- Geeks Disappointed that RTX 4080/4090 doesn’t come with PCIe 5.0
- What are advantages and disadvantages of different load balancing?
Fedora Linux Rawhide kernel performance is extremely poor due to too many debug options.
Fedora Linux provides a number of debugging options during its “Rawhide” development phase to diagnose problems during testing.
But Richard Jones, a Linux developer at Red Hat, found that these debug options cost a lot of performance, making the Fedora Rawhide kernel incredibly slow.
The current Fedora Rawhide kernel is too slow to run libguestfs tests with Koji builds.
They run in a qemu VM, running the Rawhide kernel, emulated using software virtualization (TCG). But now it times out frequently because these kernel debugging options are just too slow.
Richard Jones then examines the performance cost of various debugging options used by the Rawhide kernel.
It was found that the Fedora Rawhide kernel with all debug options increased the test case runtime by 143%, from 12.3 seconds without debug options to over 30 seconds.
According to foreign media Phoronix , the debugging options that currently have the greatest impact on Fedora Rawhide kernel performance include:
- PROVE_LOCKING
- LOCK_STAT
- DEBUG_WW_MUTEX_SLOWPATH
- DEBUG_KMEMLEAK
- DEBUG_LOCK_ALLOC
- PAGE_TABLE_CHECK_ENFORCED
Richard Jones outlines his test results on the Fedora kernel mailing list and has an extensive discussion of debugging options for the Fedora Rawhide kernel.
He wants to check whether these kernel debugging options are degraded upstream, causing the performance of the Fedora Rawhide kernel to plummet, and is also considering whether to drop some expensive debugging options.
- DIY a PBX (Phone System) on Raspberry Pi
- How to host multiple websites on Raspberry Pi 3/4?
- A Free Intercom/Paging system with Raspberry pi and old Android phones
- DIY project: How to use Raspberry Pi to build DNS server?
- Raspberry Pi project : How to use Raspberry Pi to build git server?
