Announcement

Collapse
No announcement yet.

Fedora Developers Are Trying To Figure Out The Best Linux I/O Scheduler

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Only if the graphical tool shows performance numbers such as read and write bandwidth and 95% and 99% read, write and sync write latency.

    Numbers from the filesystem would be good too. Time to complete an open call, a read, a write and fsync.

    Without data what good is a tool to pick random options?

    Comment


    • #12
      Btw, years ago there was also interest in comparing slab allocators (SLUB, SLAB, SLOB, and a new one called SLQB or something like that), but it seems we've defaulted to SLUB and forgot about them.
      Last edited by halo9en; 15 December 2018, 02:52 AM.

      Comment


      • #13
        Originally posted by Candy View Post
        At the end they'll come up with an own implementation made by the systemd guys.
        Systemd-sched - it will run in userspace (as a huge monolithic processs 1) and communicate via XML messages over D-BUS and Avahi.

        Comment


        • #14
          Originally posted by tildearrow View Post
          It is best to have 2 default schedulers: one for classic hard disks and one for SSD's.
          Arch and presumably others have that done by udev rules, see /etc/udev/rules.d/60-schedulers.rules


          Comment


          • #15
            Arch doesn't touches any schedulers. /etc/udev/rules.d/60-schedulers.rules is user custom config.

            Comment


            • #16
              Thus might not be liked by some but the default should be for the scheduler giving the best desktop performance. The theory here is that desktop users would be leAst likely to want to tune or know how to tune their systems. Server administrators and such should know and thus the defaults mean nothing.

              Sometimes people make mountains out of mole hills. This seems to be a classic example. Beyond all of this Fedora could add a web page that explains the configuration possibilities in detail. Documentation can significantly reduce the mystery for users here.

              Comment


              • #17
                Originally posted by wizard69 View Post
                Thus might not be liked by some but the default should be for the scheduler giving the best desktop performance. The theory here is that desktop users would be leAst likely to want to tune or know how to tune their systems. Server administrators and such should know and thus the defaults mean nothing.
                Also, there are server editions of many Linux distributions, including Fedora. So the majority of the edition where the desktop is the focus will be used by desktop users.

                Comment


                • #18
                  Originally posted by FlawlessVolcano View Post
                  Arch doesn't touches any schedulers. /etc/udev/rules.d/60-schedulers.rules is user custom config.
                  My mistake.
                  _Some_ distros have an udev rule for io schedulers.
                  I'm on on antergos and presumed it was an arch ting.

                  Comment


                  • #19
                    Originally posted by caligula View Post

                    Systemd-sched - it will run in userspace (as a huge monolithic processs 1) and communicate via XML messages over D-BUS and Avahi.
                    Good! It will mesh well with the systemd's sd-dbus implementation

                    Comment


                    • #20
                      Originally posted by hreindl View Post

                      systemd is not monolithic - what about morons like you inform yourself about basics instead appear in the public like this?
                      Ever heard of humor, pal?

                      Comment

                      Working...
                      X