Announcement

Collapse
No announcement yet.

MQ-Deadline Scheduler Optimized For Much Better Scalability

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

  • MQ-Deadline Scheduler Optimized For Much Better Scalability

    Phoronix: MQ-Deadline Scheduler Optimized For Much Better Scalability

    Days after delivering a nice boost to Linux I/O performance, Linux storage expert Jens Axboe has tackled another storage-related bottleneck within the kernel...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    It might not be a "one-liner simple fix" since the code patch is longer than that, but still ... it's nice to see improvements like this.

    Comment


    • #3
      Awesome!

      Comment


      • #4
        i think something like this went unnoticed for so long because people will just use noop for scheduling on nvme. I use mq-deadline on my sata ssds, and bfq on my spinning rust.

        Comment


        • #5
          mq-deadline is the default on my SATA SSD on Ubuntu 23.10:
          Code:
          $ cat /sys/block/sda/queue/scheduler
          none [mq-deadline]
          ​

          Comment


          • #6
            Originally posted by oibaf View Post
            mq-deadline is the default on my SATA SSD on Ubuntu 23.10:
            Code:
            $ cat /sys/block/sda/queue/scheduler
            none [mq-deadline]
            ​
            Seems BFQ isn't included by default. A shame, since mq-deadline does not support io prioritisation or cgroups io.weight.
            ​​​

            Comment


            • #7
              Originally posted by S.Pam View Post
              Seems BFQ isn't included by default. A shame, since mq-deadline does not support io prioritisation or cgroups io.weight.
              ​​​
              It might be a module. Just try and enable it and see if it sticks. If name is bad or module is unavailable, it will not make changes.

              Code:
              echo -n 'bfq' | sudo tee /sys/block/sda/queue/scheduler

              Comment


              • #8
                Originally posted by cobratbq View Post

                It might be a module. Just try and enable it and see if it sticks. If name is bad or module is unavailable, it will not make changes.

                Code:
                echo -n 'bfq' | sudo tee /sys/block/sda/queue/scheduler
                Yea. Maybe. I don't use Ubuntu much myself and I have BFQ on my systems where suitable. Just meant it in a general sense.

                Comment


                • #9
                  Originally posted by fitzie View Post
                  i think something like this went unnoticed for so long because people will just use noop for scheduling on nvme. I use mq-deadline on my sata ssds, and bfq on my spinning rust.
                  Based on https://github.com/pop-os/default-settings/pull/149 it may be better to use kyber for nvme on desktop.

                  Comment


                  • #10
                    Originally posted by geearf View Post

                    Based on https://github.com/pop-os/default-settings/pull/149 it may be better to use kyber for nvme on desktop.
                    It seems many like Kyber. Do you know if it supports io weights like BFQ?

                    Comment

                    Working...
                    X