dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109171] AMD's GPU is Slower than Intel's
Date: Sat, 29 Dec 2018 14:48:00 +0000	[thread overview]
Message-ID: <bug-109171-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1912 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109171

            Bug ID: 109171
           Summary: AMD's GPU is Slower than Intel's
           Product: Mesa
           Version: 18.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: ali.sherif10@yahoo.com
        QA Contact: dri-devel@lists.freedesktop.org

glxgears and CS: Go are much slower with AMD's GPU. Performance's much higher
with Intel's.

Outputs:
$ glxgears
306 frames in 5.0 seconds = 61.029 FPS
299 frames in 5.0 seconds = 59.761 FPS
299 frames in 5.0 seconds = 59.762 FPS
299 frames in 5.0 seconds = 59.762 FPS
299 frames in 5.0 seconds = 59.762 FPS

$ DRI_PRIME=1 glxgears
304 frames in 5.0 seconds = 60.666 FPS
299 frames in 5.0 seconds = 59.762 FPS
299 frames in 5.0 seconds = 59.762 FPS
299 frames in 5.0 seconds = 59.763 FPS
299 frames in 5.0 seconds = 59.760 FPS

$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
32606 frames in 5.0 seconds = 6521.047 FPS
31516 frames in 5.0 seconds = 6302.010 FPS
32145 frames in 5.0 seconds = 6428.891 FPS
31443 frames in 5.0 seconds = 6288.595 FPS
31029 frames in 5.0 seconds = 6205.721 FPS

$ DRI_PRIME=1 vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
12031 frames in 5.0 seconds = 2406.195 FPS
10110 frames in 5.0 seconds = 2021.870 FPS
10122 frames in 5.0 seconds = 2022.474 FPS
9782 frames in 5.0 seconds = 1956.206 FPS
10175 frames in 5.0 seconds = 2034.901 FPS


Laptop: HP Pavilion g6.
AMD's GPU: Radeon HD 7670M.
OS: 64-bit Linux (Fedora 29 KDE Spin).

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

[-- Attachment #1.2: Type: text/html, Size: 3269 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-12-29 14:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 14:48 bugzilla-daemon [this message]
2018-12-29 15:24 ` [Bug 109171] AMD's GPU is Slower than Intel's bugzilla-daemon
2018-12-29 17:27 ` bugzilla-daemon
2018-12-29 17:36 ` bugzilla-daemon
2018-12-29 17:37 ` bugzilla-daemon
2019-01-03  3:16 ` bugzilla-daemon
2019-01-03  3:17 ` bugzilla-daemon
2019-01-03  8:34 ` bugzilla-daemon
2019-01-03 12:16 ` bugzilla-daemon
2019-01-03 12:16 ` bugzilla-daemon
2019-01-03 12:25 ` bugzilla-daemon
2019-01-03 12:34 ` bugzilla-daemon
2019-01-03 12:34 ` bugzilla-daemon
2019-01-03 12:39 ` bugzilla-daemon
2019-01-03 12:42 ` bugzilla-daemon
2019-01-03 13:36 ` bugzilla-daemon
2019-09-18 19:26 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109171-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox