Announcement

Collapse
No announcement yet.

Early Independent Benchmarks Of The MuQSS Scheduler

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

  • Early Independent Benchmarks Of The MuQSS Scheduler

    Phoronix: Early Independent Benchmarks Of The MuQSS Scheduler

    MuQSS is the successor to the BFS scheduler and its first major release was last month for this scheduler that currently doesn't have any ambitions to go mainline. On OpenBenchmarking.org this weekend were some independent benchmarks of the new scheduler...

    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
    why are the MuQSS runs done at a lower kernel tick ?
    lack of consistency w.r.t. testing -> invalid results

    Comment


    • #3
      Originally posted by Naib View Post
      why are the MuQSS runs done at a lower kernel tick ?
      lack of consistency w.r.t. testing -> invalid results
      Because Con Kolivas (the author) recommends 100Hz for optimal performance of MuQSS whereas CFS upstream recommend 1000Hz. In each case, the default is set to match.
      It's a fair comparison to use each system's recommended/default values.

      Originally posted by MuQSS 0.120 release notes
      MuQSS is now a tickless scheduler. That means it can maintain its guaranteed low latency even in a build configured with a low Hz tick rate. To that end, it is now defaulting to 100Hz, and it is recommended to use this as the default choice for it leads to more throughput and power savings as well.
      (my emphasis)

      Comment


      • #4
        Originally posted by Naib View Post
        why are the MuQSS runs done at a lower kernel tick ?
        lack of consistency w.r.t. testing -> invalid results
        http://ck-hack.blogspot.com.by/2016/10/linux-48-ck5-muqss-version-0120.html
        - MuQSS is now a tickless scheduler. That means it can maintain its guaranteed low latency even in a build configured with a low Hz tick rate. To that end, it is now defaulting to 100Hz, and it is recommended to use this as the default choice for it leads to more throughput and power savings as well.

        Comment


        • #5
          @Michael: You can't "vouge" for them or you can't "vouch" for them? Also the graphs have no units on them, so I have no idea what I am looking.

          Comment


          • #6
            (at least 5 chars)

            Comment


            • #7
              Originally posted by droste View Post
              (at least 5 chars)
              What??

              Comment


              • #8
                droste Thanks for the highlight. I had to push ctrl+shift+'+' 4 times to see that, that was text an not just a blue line. There seems to be enough white space for at least 8pt font.

                Comment


                • #9
                  Originally posted by xnor View Post
                  What??
                  You can't just post a picture, you have to have at least some amount of text Probably against spam.

                  Comment


                  • #10
                    MuQSS?

                    Eww.

                    Comment

                    Working...
                    X