News: 0001638201

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Benchmarking The BORE Scheduler Performance With CachyOS Linux

([Operating Systems] 3 Hours Ago 4 Comments)


[1]

Earlier this week I ran [2]benchmarks of different CachyOS Linux kernel flavors that proved interesting from the performance overhead of their hardened kernel build to various other interesting performancr takeaways. One kernel flavor I hadn't tested though was their build with the BORE scheduler. Given the interest and feedback from Phoronix readers, here is an article focused on looking at the performance of the BORE scheduler for the Linux kernel on CachyOS.

[3]

The BORE scheduler is short ofr the "Burst-Oriented Response Enhancer" and is optimized for bursty workloads, which can be great for desktop responsiveness and similar scenarios. [4]The BORE scheduler's GitHub repository describes itself as:

"BORE (Burst-Oriented Response Enhancer) is an enhanced versions of the EEVDF (Earliest Eligible Virtual Deadline First) Linux schedulers. Developed with the aim of maintaining these schedulers' high performance while delivering resilient responsiveness to user input under as versatile load scenario as possible.

To achieve this, BORE introduces a dimension of flexibility known as "burstiness" for each individual tasks, partially departing from CFS's inherent "complete fairness" principle. Burstiness refers to the score derived from the accumulated CPU time a task consumes after explicitly relinquishing it, either by entering sleep, IO-waiting, or yielding. This score represents a broad range of temporal characteristics, spanning from nanoseconds to hundreds of seconds, varying across different tasks.

Leveraging this burstiness metric, BORE dynamically adjusts scheduling properties such as weights and delays for each task. Consequently, in systems experiencing diverse types of loads, BORE prioritizes tasks requiring high responsiveness, thereby improving overall system responsiveness and enhancing the user experience."

On CachyOS, installing linux-cachyos-bore is their default kernel build with the BORE scheduler patch applied.

I hadn't tested this configuration specifically as part of my earlier CachyOS kernel comparison due to time/resource constraints. Given the reader interest and still having the System76 Thelio Major system in the same setup on CachyOS as the prior round of tests, here are the benchmarks with the CachyOS BORE kernel compared to the other kernel flavors across a wide variety of benchmarks.



[1] https://www.phoronix.com/image-viewer.php?id=cachyos-bore&image=cachyos_bore_1_lrg

[2] https://www.phoronix.com/review/cachyos-linux-flavors

[3] https://www.phoronix.com/image-viewer.php?id=cachyos-bore&image=cachyos_bore_2_lrg

[4] https://github.com/firelzrd/bore-scheduler



Severe Acronym Shortage Cripples Computer Industry

SILICON VALLEY, CALIFORNIA (SVC) -- According to a recent study by the
Blartner Group, 99.5% of all possible five letter combinations have
already been appropriated for computer industry acronyms. The impending
shortage of 5LC's is casting a dark shadow over the industry, which relies
heavily on short, easy-to-remember acronyms for everything.

"Acronym namespace collisions (ANCs) are increasing at a fantastic rate
and threaten the very fabric of the computing world," explained one ZD
pundit. "For example, when somebody talks about XP, I don't know whether
they mean eXtreme Programming or Microsoft's eXceptionally Pathetic
operating system. We need to find a solution now or chaos will result."

Leaders of several SVC companies have floated the idea of an
"industry-wide acronym conservation protocol" (IWACP -- one of the few
5LCs not already appropriated). Explained Bob Smith, CTO of IBM, "If
companies would voluntarily limit the creation of new acronyms while
recycling outdated names, we could reduce much of the pollution within the
acronym namespace ourselves. The last thing we want is for Congress to get
involved and try to impose a solution for this SAS (Severe Acronym
Shortage) that would likely only create many new acronyms in the process."