[Bug 60911] New: performance regression with ioquake3 based engines

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=60911

            Bug ID: 60911
           Summary: performance regression with ioquake3 based engines
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.11.0
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: bugs at ttyhoney.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Hello!

It seems like from kernel 3.10.10 to kernel 3.11.0 the performance decreased
around 5% to 15% in ioquake3 based games. I regulary run benchmarks with
ioquake3, because it is the base for a lot of games. My setup:

file ~/.drirc # turns off vsync. don't use the driconf for this, it will set
the wrong driver.

<device screen="0" driver="dri2">
    <application name="Default">
        <option name="vblank_mode" value="0"/>
    </application>
</device>

$ ./quake3
~ # opens console
timedemo 1
demo four
~ # read fps

With the last kernels and drivers I got always a framerate between
295fps-305fps. With the new kernel 3.11.0 the performance decreased to 255fps
to 275fps i.e. it runs slower and the range is also bigger.

I wondered if the new WQ_POWER_EFFICIENT_DEFAULT caused this and turned it on
and off, but it is not responsible. A downgrade to kernel 3.10.10 fixed the
regression, so it seems not caused by the userspace-driver or unredirection
(window-manager).

Phoronix is controversial resource. But in this case it confirms my own
results. I should mention, that "World of Padman" is based on IOQuake3:
http://www.phoronix.com/scan.php?page=news_item&px=MTQxMTM

Thank you

PS:
Regulary the performance increases a little bit with a new kernel or
userspace-driver. I'm always happy to see some fps more after running a
benchmark :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.