CachyOS scx-sheduler is fantastic!

General
61

You re kidding me ! Just kidding @indy ,

CrunchBang, ArchCraft, ArchLabs, BunsenLabs , & loads of other distros all have those by defaults & are with OpenBox as well.

1 Like
62

It shows how long I have been in the Linux seen :smiling_face: Respect to you!

1 Like
63

Well , you re already better than me after 3-4 years ! lol

1 Like
64

I find the Linux scene so vast. We all can go down the rabbit hole of our choice. Windows is not this much fun. Are you into Vim or Emacs, init system wars, rolling release or fixed, x11 or Wayland, etc? You know what I mean? :laughing:

1 Like
65

It s what I m doing with my desktop !lol

It was supposed to be some cheap secondhand parts picked here & there, bet that it s not going the way it was supposed too ! lol

1 Like
66

You can use this command scx_lavd --help to get help about the different flags available with LAVD.

Here are the parts that interest us in our case :

āÆ scx_lavd --help
      --autopilot
          Automatically decide the scheduler's power mode based on system load. This is a default mode if you don't specify the following options:

      --autopower
          Automatically decide the scheduler's power mode based on the system's energy profile

      --performance
          Run in performance mode to get maximum performance

      --no-core-compaction
          Disable core compaction and schedule tasks across all online CPUs. Core compaction attempts to keep idle CPUs idle in favor of scheduling tasks on CPUs that are already awake. See main.bpf.c for more info. Normally set by the
          power mode, but can be set independently if desired

Even more documentation is available in the source code, if you are interested you can read the first 182 lines of this file : scx/scheds/rust/scx_lavd/src/bpf/main.bpf.c at main Ā· sched-ext/scx Ā· GitHub

Basically, --performance is pretty straightforward, it make zero compromise on performance. --no-core-compaction disable core compaction which is a feature meant to save power, which is the opposite of ā€œperformanceā€.

By using --performance --no-core-compaction you ask the scheduler to use maximum power for optimum performances. On a device using a battery like the Steam Deck, it might not be the best choice. In my case, those settings are used on a desktop having a 1000w PSU, so I aim for best performance over power saving.

I donā€™t use --autopilot and --autopower because they have ā€œautoā€ in their names! Most of the time, things having ā€œautoā€ in their names have an overhead at runtime.

1 Like
67

Oh, thx for that @iSpeakVeryWell , some readings to do !

I also happen to have one 1000 watt psu on my end. & a spare 1050 w also.

68

Thatā€™s a great news! Iā€™m glad I was able to help! :smiley:

1 Like
69

As autotragic transmissions ! lol Just kidding.

1 Like