All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106175] amdgpu.dc=1 shows performance issues with Xorg compositors when moving windows
Date: Mon, 19 Nov 2018 03:22:14 +0000	[thread overview]
Message-ID: <bug-106175-502-d2DxO2guZk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106175-502@http.bugs.freedesktop.org/>


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

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

--- Comment #45 from rropid@gmail.com ---
(In reply to bmilreu from comment #43)
> If devs want an easy test case, use these links for reproducing it in
> chromium:
> 
> https://www.vsynctester.com/
> https://www.testufo.com/photo
> https://www.slither.io
> 
> move the cursor around, move/resize some windows. you will notice it
> 
> the vsync/cursor stutters and frame-skips are pretty noticeable with dc=1 on
> all three links
> 
> KWin, compton, TearFree, mutter, xfwm4 all have the same problems.

I just tried dc=1 and I only seem to have a problem if I use TearFree. Things
are totally fine without TearFree.

To be clear about what I'm doing here right now:

I made sure DC is enabled:

  $ systool -vm amdgpu | grep dc
      dc                  = "1"
  $ dmesg | grep -i display
  [    1.014297] [drm] Display Core initialized with v3.1.59!

I removed TearFree from my X config:

  $ cat /etc/X11/xorg.conf.d/20-amdgpu.conf 
  Section "OutputClass"
      Identifier "my amdgpu settings"
      MatchDriver "amdgpu"
      Option "DRI" "3"
  EndSection

And I started Compton like this to make sure it's a clean config:

  $ compton --config /dev/null --backend glx --vsync opengl

With this setup, I don't seem to have any stutter. I visited the websites you
mention in a Chromium window, then opened another window and tried moving
things around and resizing. It behaves fine, same as what I know from normally
using dc=0.

Kernel is 4.19.2, Mesa 18.2.4, Xorg 1.20.3, the GPU is a RX480, monitor is 60
Hz.

After I had typed this, I have now added TearFree to the X config and restarted
X:

  $ cat /etc/X11/xorg.conf.d/20-amdgpu.conf 
  Section "OutputClass"
      Identifier "my amdgpu settings"
      MatchDriver "amdgpu"
      Option "TearFree" "true"
      Option "DRI" "3"
  EndSection

Now, with TearFree enabled, things are super terrible. Trying to move a window
around has extreme stutter, it seems to drop frames. If I restart Compton with
"GALLIUM_HUD=fps" and then try moving a window around in circles, I can see it
stays below 40 fps instead of hitting the 60 fps that it should be running at.

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

[-- Attachment #1.2: Type: text/html, Size: 3502 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

  parent reply	other threads:[~2018-11-19  3:22 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-22 11:05 [Bug 106175] amdgpu.dc=1 shows performance issues with Xorg compositors when moving windows bugzilla-daemon
2018-04-22 11:05 ` bugzilla-daemon
2018-04-23  9:52 ` bugzilla-daemon
2018-04-23  9:56 ` bugzilla-daemon
2018-04-23 11:08 ` bugzilla-daemon
2018-04-23 11:56 ` bugzilla-daemon
2018-04-24 14:30 ` bugzilla-daemon
2018-04-24 14:34 ` bugzilla-daemon
2018-04-24 14:57 ` bugzilla-daemon
2018-04-24 16:56 ` bugzilla-daemon
2018-04-24 17:26 ` bugzilla-daemon
2018-04-24 23:14 ` bugzilla-daemon
2018-04-30 12:49 ` bugzilla-daemon
2018-05-18 14:47 ` bugzilla-daemon
2018-05-26 12:47 ` bugzilla-daemon
2018-05-28  8:42 ` bugzilla-daemon
2018-05-28  9:27 ` bugzilla-daemon
2018-06-03 23:03 ` bugzilla-daemon
2018-06-06  7:59 ` bugzilla-daemon
2018-06-15 13:54 ` bugzilla-daemon
2018-06-15 14:02 ` bugzilla-daemon
2018-06-15 14:17 ` bugzilla-daemon
2018-07-21 12:42 ` bugzilla-daemon
2018-07-27 14:32 ` bugzilla-daemon
2018-07-31 12:22 ` bugzilla-daemon
2018-09-11 17:57 ` bugzilla-daemon
2018-09-11 18:23 ` bugzilla-daemon
2018-09-11 22:05 ` bugzilla-daemon
2018-10-14 12:38 ` bugzilla-daemon
2018-10-15 13:22 ` bugzilla-daemon
2018-10-24 20:26 ` bugzilla-daemon
2018-10-31 23:17 ` bugzilla-daemon
2018-11-01 11:11 ` bugzilla-daemon
2018-11-01 12:26 ` bugzilla-daemon
2018-11-01 12:30 ` bugzilla-daemon
2018-11-01 15:32 ` bugzilla-daemon
2018-11-01 17:51 ` bugzilla-daemon
2018-11-01 18:01 ` bugzilla-daemon
2018-11-01 18:15 ` bugzilla-daemon
2018-11-01 18:40 ` bugzilla-daemon
2018-11-02  0:21 ` bugzilla-daemon
2018-11-02 10:48 ` bugzilla-daemon
2018-11-08  5:35 ` bugzilla-daemon
2018-11-19  0:40 ` bugzilla-daemon
2018-11-19  1:28 ` bugzilla-daemon
2018-11-19  1:48 ` bugzilla-daemon
2018-11-19  3:22 ` bugzilla-daemon [this message]
2018-11-19 16:09 ` bugzilla-daemon
2018-11-19 16:19 ` bugzilla-daemon
2018-11-19 16:44 ` bugzilla-daemon
2018-11-19 16:53 ` bugzilla-daemon
2018-11-19 21:14 ` bugzilla-daemon
2018-11-19 21:33 ` bugzilla-daemon
2018-11-19 22:48 ` bugzilla-daemon
2018-11-20  0:35 ` bugzilla-daemon
2018-11-20  9:10 ` bugzilla-daemon
2018-11-21 23:53 ` bugzilla-daemon
2018-11-22  1:22 ` bugzilla-daemon
2018-11-22  1:41 ` bugzilla-daemon
2018-11-22 14:32 ` bugzilla-daemon
2018-11-22 15:32 ` bugzilla-daemon
2018-11-22 16:09 ` bugzilla-daemon
2018-11-22 17:31 ` bugzilla-daemon
2018-11-22 18:51 ` bugzilla-daemon
2018-11-22 19:09 ` bugzilla-daemon
2018-11-22 19:30 ` bugzilla-daemon
2018-11-22 21:00 ` bugzilla-daemon
2018-11-22 21:33 ` bugzilla-daemon
2018-11-24 15:24 ` bugzilla-daemon
2018-11-24 18:30 ` bugzilla-daemon
2018-11-24 19:38 ` bugzilla-daemon
2018-11-24 20:07 ` bugzilla-daemon
2018-11-28 21:28 ` bugzilla-daemon
2018-11-29  1:32 ` bugzilla-daemon
2018-11-30 12:35 ` bugzilla-daemon
2018-12-04 23:18 ` bugzilla-daemon
2018-12-07 10:24 ` bugzilla-daemon
2018-12-07 16:55 ` bugzilla-daemon
2018-12-07 21:25 ` bugzilla-daemon
2018-12-12 21:29 ` bugzilla-daemon
2018-12-25  5:49 ` bugzilla-daemon
2019-01-10 18:49 ` bugzilla-daemon
2019-01-10 19:04 ` bugzilla-daemon
2019-01-10 19:30 ` bugzilla-daemon
2019-01-10 19:31 ` bugzilla-daemon
2019-01-11  8:56 ` bugzilla-daemon
2019-01-11 19:33 ` bugzilla-daemon
2019-01-11 22:13 ` bugzilla-daemon
2019-01-12  1:12 ` bugzilla-daemon
2019-01-12 16:21 ` bugzilla-daemon
2019-01-12 16:57 ` bugzilla-daemon
2019-01-12 16:58 ` bugzilla-daemon
2019-01-12 17:41 ` bugzilla-daemon
2019-01-12 18:12 ` bugzilla-daemon
2019-01-12 19:01 ` bugzilla-daemon
2019-01-14 11:08 ` bugzilla-daemon
2019-01-14 21:17 ` bugzilla-daemon
2019-01-15 13:52 ` bugzilla-daemon
2019-01-15 14:53 ` bugzilla-daemon
2019-01-15 17:52 ` bugzilla-daemon
2019-01-15 18:16 ` bugzilla-daemon
2019-01-15 20:07 ` bugzilla-daemon
2019-01-15 21:44 ` bugzilla-daemon
2019-01-15 22:20 ` bugzilla-daemon
2019-01-16 18:27 ` bugzilla-daemon
2019-01-17  8:38 ` bugzilla-daemon
2019-03-07 23:54 ` 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-106175-502-d2DxO2guZk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.