amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Javad Karabi <karabijavad@gmail.com>
To: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: slow rx 5600 xt fps
Date: Tue, 19 May 2020 13:59:27 -0500	[thread overview]
Message-ID: <CAEOHGOm=g_VGa5939Qi_HEXAfuUKuy3tXURx9TKg+n==dUDqPQ@mail.gmail.com> (raw)

given this setup:
laptop -thunderbolt-> razer core x -> xfx rx 5600 xt raw 2 -hdmi-> monitor
DRI_PRIME=1 glxgears gears gives me ~300fps

given this setup:
laptop -thunderbolt-> razer core x -> xfx rx 5600 xt raw 2
laptop -hdmi-> monitor

glx gears gives me ~1800fps

this doesnt make sense to me because i thought that having the monitor
plugged directly into the card should give best performance.

theres another really weird issue...

given setup 1, where the monitor is plugged in to the card:
when i close the laptop lid, my monitor is "active" and whatnot, and i
can "use it" in a sense

however, heres the weirdness:
the mouse cursor will move along the monitor perfectly smooth and
fine, but all the other updates to the screen are delayed by about 2
or 3 seconds.
that is to say, its as if the laptop is doing everything (e.g. if i
open a terminal, the terminal will open, but it will take 2 seconds
for me to see it)

its almost as if all the frames and everything are being drawn, and
the laptop is running fine and everything, but i simply just dont get
to see it on the monitor, except for one time every 2 seconds.

its hard to articulate, because its so bizarre. its not like, a "low
fps" per se, because the cursor is totally smooth. but its that
_everything else_ is only updated once every couple seconds.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

             reply	other threads:[~2020-05-19 18:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:59 Javad Karabi [this message]
2020-05-19 19:13 ` slow rx 5600 xt fps Alex Deucher
2020-05-19 19:20   ` Javad Karabi
2020-05-19 19:44     ` Javad Karabi
2020-05-19 20:01       ` Javad Karabi
2020-05-19 21:34         ` Alex Deucher
2020-05-19 21:13       ` Alex Deucher
2020-05-19 21:22         ` Javad Karabi
2020-05-19 21:42           ` Alex Deucher
2020-05-20  1:16             ` Javad Karabi
2020-05-20  1:19               ` Javad Karabi
2020-05-20  1:20               ` Bridgman, John
2020-05-20  1:35                 ` Javad Karabi
2020-05-20  2:29               ` Alex Deucher
2020-05-20 22:04                 ` Javad Karabi
2020-05-21  3:11                   ` Alex Deucher
2020-05-21 19:03                     ` Javad Karabi
2020-05-21 19:15                       ` Alex Deucher
2020-05-21 21:21                         ` Javad Karabi
2020-05-22 22:48                           ` Javad Karabi
2020-05-23 10:17                             ` Michel Dänzer
2020-05-25  1:03                               ` Javad Karabi
2020-05-25  1:29                                 ` Javad Karabi
2020-05-19 21:32     ` Alex Deucher

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='CAEOHGOm=g_VGa5939Qi_HEXAfuUKuy3tXURx9TKg+n==dUDqPQ@mail.gmail.com' \
    --to=karabijavad@gmail.com \
    --cc=amd-gfx@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;
as well as URLs for NNTP newsgroup(s).