Announcement

Collapse
No announcement yet.

Linux 3.7 + Mesa 9.1-devel Running On Ubuntu 12.10

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

  • Linux 3.7 + Mesa 9.1-devel Running On Ubuntu 12.10

    Phoronix: Linux 3.7 + Mesa 9.1-devel Running On Ubuntu 12.10

    For those Intel Sandy Bridge owners wondering if there's any worthwhile performance improvements when upgrading from Ubuntu 12.10 with Mesa 9.0 and the Linux 3.5 kernel up to the early Mesa 9.1-devel state with the Linux 3.7 Git kernel, here are some benchmarks...

    http://www.phoronix.com/vr.php?view=MTIwNTU

  • #2
    You can play Doom 3 with those frames actually, but you also fail to consider the fact that those are from an Intel IGP. Please read the article rather than using it merely as an excuse to pimp an idea.

    Comment


    • #3
      Doom 3 was set for 30 fps on console, so yes it is playable.

      Comment


      • #4
        Originally posted by Paradox Uncreated View Post
        Stunt Car Racer on amiga500 was also playable. It was 5 fps.
        ...so framerates aren't necessarily important?

        Comment


        • #5
          I guess the Doom3 benchmarks which are not using ultra settings have got rendering issues. I tested mesa 8.0.4 and 9.0 and got em. The problem you see easyly in the timedemo when the flashlight is used:

          http://kanotix.com/files/fix/tmp/dhewm3/ivy.jpg

          I tested sandy and ivy bridge, doom3 native and dhewm3.

          Comment


          • #6
            I notice it says 61 FPS though - what do you usually get?

            Comment


            • #7
              I forgot the exact numbers, but they are in the lower 20s @ 1920x1200 with ivy bridge, dhewm3 64 bit is a bit slower than doom3 32 bit. sandy bridge hd 2000 (i7-2600) has 29.x fps using ultra settings @ 1280x1024 (which are default for dhewm3). Now i play the game a bit with nvidia gt630 (kepler) @ 1920x1200 there i get easyly 60 fps. You can test it like that without pts:
              Code:
              doom3 +set r_mode -1 +set r_customwidth 1920 +set r_customheight 1200 +set com_showfps 1 +timedemoquit demo1

              Comment


              • #8
                Originally posted by Paradox Uncreated View Post
                You can play doom3 at 36 fps? Not really.
                Have you ever even played Doom3? It runs just fine at 30fps - as long as that's the minimum, and it's not consistently dipping down into the teens.

                Doom3 isn't a twitch shooter that requires 60fps.

                Comment


                • #9
                  Not to bash your work on configuring CFS, but I think the behavior you're looking for in CFS has already been attained in BFS. For instance, when BFS was still in development, I worked with Con to make sched_yield always take precedence over other loads. This makes iD Tech engines (Quake 3, Doom 3), and games like Savage 2, all run "smooth". This is very important since almost all applications using sched_yield to process frames are all 3D games that rely on low latency frame rendering. A good game to observe this behavior is Warsow - try playing this game on BFS and CFS with your adjustments with a high definition youtube video playing on a second monitor. This game is especially sensitive to anomalies in poor behavior to sched_yield calls.

                  Smooth is defined as no jitter, kind of like what Google was trying to attain with Project Butter, where the application rendering animated graphics does not suddenly lose frames due to another process preempting the process rendering the screen.

                  You can check some work done to achieve this a bit further on http://github.com/damentz/zen-kernel (http://git.zen-kernel.org/stable/ is currently down) under the zen-tune branch. In this branch, we create profiles where we reduce the context switching time from 6ms+ on CFS to 3ms, and also set BFS' 6ms round robin interval down to 3ms. There's no fancy code changing here, only new defaults.

                  Direct commit link for Linux 3.5: https://github.com/damentz/zen-kerne...606e272e6e0946

                  A notice to beware for users with old CPUs though, rapid context switching can increase L2 cache misses on older generation processors. This is especially evident on android phones, where setting the rr_interval below 8ms on the Snapdragon CPU available on the Nexus One causes poor raw throughput that's required to run things like Gameboid to emulate GBA games. This throughput loss is immeasurable on new CPUs like the Core 2 Duo, however. I did a few benchmarks on my laptop and couldn't find a difference outside a measurement of error (below 1-0.5%).

                  An FYI for any Debian users here, all these changes are already available under the Liquorix kernel, which uses the newest Zen Kernel sources.

                  Comment

                  Working...
                  X