Announcement

Collapse
No announcement yet.

BFQ I/O Scheduler Queued For Linux 4.12

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

  • #11
    Originally posted by Pawlerson View Post

    Same here. I didn't use bfq, but enabling blkmq helps cfq a lot. Performs much better than Win7.
    Enabling blk-mq just disables scheduling at all now. So, congratulations, CFQ has nothing to do with this.

    Comment


    • #12
      Originally posted by Pawlerson View Post
      Same here. I didn't use bfq, but enabling blkmq helps cfq a lot. Performs much better than Win7.
      It doesn't take much to outperform Windows in this regard. All Windows versions from 7 to 10 just stall completely here if I start a big copy or decompression task. Want to un-7z a 10GB file? The desktop becomes completely frozen for several minutes on end...

      It's utter garbage :-P

      On Linux, and especially with BFQ, I don't even notice the copy/unpack operation is going on.

      Comment


      • #13
        waiting for bfq-mq for my ssd

        Comment


        • #14
          Why BFQ won't be the default scheduler?

          Comment


          • #15
            Originally posted by Pawlerson View Post

            Good news. Windows stalls even with Steam. I'd love to see schedulers performance and latency comparison.
            I never had this problem on windows 10 on my laptop...

            Comment


            • #16
              Originally posted by Azrael5 View Post
              Why BFQ won't be the default scheduler?
              Because Linux's main target isn't desktop, apparently. It took an awful fucking huge lot of time to get this merged as optional scheduler.

              Comment


              • #17
                This is great, I can finally (eventually) show off to OSX users that keep annoying me with how on OSX is so smooth even with multiple programs open.

                Originally posted by RealNC View Post
                It doesn't take much to outperform Windows in this regard. All Windows versions from 7 to 10 just stall completely here if I start a big copy or decompression task. Want to un-7z a 10GB file? The desktop becomes completely frozen for several minutes on end...
                Agreed. Another fun one is opening a folder with say 3-4k sub-megabyte image files and waiting to eventually see thumbnails (a few hours later).

                I've been using programs like FastCopy on Windows because it manages to move files without locking up the system (and are even significantly faster than normal copy-paste).

                Comment


                • #18
                  Originally posted by Marc Driftmeyer View Post
                  And here I wonder when Debian will finish with 9.0 so I can try out 4.10.
                  Newer kernel will be available from backports anyway. (That's how I'm getting my kernels on Debian Jessie)


                  Originally posted by sarfarazahmad View Post
                  i moved to blkmq sometime back and enabled it on all layers dm/scsi. i found it to perform better than bfq at least for this use case
                  Originally posted by post-factum View Post
                  Enabling blk-mq just disables scheduling at all now. So, congratulations, CFQ has nothing to do with this.
                  As far as I've understood BFQ's author (paolo)'s page : BFQ *is* the only scheduler available in blkmq.

                  Part of the reason why it took so long to get BFQ into mainstream is that the author was required to re-wire it for blk-mq (on the grounds that the older queue is going to be depracated at some point in the future)

                  Comment


                  • #19
                    Originally posted by DrYak View Post

                    Newer kernel will be available from backports anyway. (That's how I'm getting my kernels on Debian Jessie)





                    As far as I've understood BFQ's author (paolo)'s page : BFQ *is* the only scheduler available in blkmq.

                    Part of the reason why it took so long to get BFQ into mainstream is that the author was required to re-wire it for blk-mq (on the grounds that the older queue is going to be depracated at some point in the future)
                    There's been a port of deadline as well during the changes to blkmq, but I don't know if it was pushed to the kernel sources or not.
                    I think that's also another big news here, we now have blkmq supporting schedulers!

                    Comment


                    • #20
                      DrYak yep quickly read through that page. i dont see any mention of bfq for blk mq. last i checked blk mq had no io schedulers and therefore it is told to have poor io performance on hdd (https://lkml.org/lkml/2015/11/25/744) but since i use hdd only as a last resort data store it works out alright

                      Comment

                      Working...
                      X