From: sylvain.bertrand@gmail.com
To: bugzilla-daemon@bugzilla.kernel.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 206231] R9 280X low performance with all games
Date: Sat, 18 Jan 2020 21:31:41 +0000 [thread overview]
Message-ID: <20200118213141.GA1027@freedom> (raw)
In-Reply-To: <bug-206231-2300-68jgyvsfvW@https.bugzilla.kernel.org/>
On Sat, Jan 18, 2020 at 08:59:14PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> I downloaded the Vulkan DLC and active the FPS in Dota 2. I get between ~80 and
> 90 fps :
I have ~ the same fps (even though it can go somewhat below in intense team fights)
> For CSGO, i get between ~70 and +100fps :
I have ~ the same for competitive maps.
For danger zone maps, namely big open maps, csgo 3d engine has disastrous
performance. Valve is aware of the problem. It seems there is a kind of cpu
cap somewhere since max or lowest 3d settings does not seem to impact
significantly the performance.
Don't forget: I heard southern island parts suffer from a critical mip mapping
bug/slowdown.
----
The real benchmark is how much time and how often the fps goes below 60 in the
worst realistic conditions (average does not matter).
----
I did re-install "rise of the tomb raider", I still get gpu vm faults.
If I recall properly "bioshock infinite" is gpu nasty even though it is a GL
game.
--
Sylvain
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-18 21:32 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 10:14 [Bug 206231] New: R9 280X low performance with all games bugzilla-daemon
2020-01-17 13:52 ` [Bug 206231] " bugzilla-daemon
2020-01-17 14:37 ` bugzilla-daemon
2020-01-17 14:49 ` bugzilla-daemon
2020-01-17 15:10 ` bugzilla-daemon
2020-01-17 15:28 ` bugzilla-daemon
2020-01-17 17:20 ` sylvain.bertrand
2020-01-17 17:21 ` bugzilla-daemon
2020-01-17 18:45 ` bugzilla-daemon
2020-01-17 19:26 ` sylvain.bertrand
2020-01-17 18:49 ` bugzilla-daemon
2020-01-17 19:27 ` bugzilla-daemon
2020-01-17 19:41 ` sylvain.bertrand
2020-01-17 19:42 ` bugzilla-daemon
2020-01-17 20:14 ` sylvain.bertrand
2020-01-17 20:14 ` bugzilla-daemon
2020-01-18 9:34 ` bugzilla-daemon
2020-01-18 14:01 ` sylvain.bertrand
2020-01-18 14:14 ` sylvain.bertrand
2020-01-18 14:02 ` bugzilla-daemon
2020-01-18 14:14 ` bugzilla-daemon
2020-01-18 15:00 ` bugzilla-daemon
2020-01-18 17:02 ` sylvain.bertrand
2020-01-18 17:02 ` bugzilla-daemon
2020-01-18 20:59 ` bugzilla-daemon
2020-01-18 21:31 ` sylvain.bertrand [this message]
2020-01-18 21:32 ` bugzilla-daemon
2020-01-19 13:11 ` bugzilla-daemon
2020-01-19 14:22 ` sylvain.bertrand
2020-01-19 14:23 ` bugzilla-daemon
2020-01-21 8:01 ` bugzilla-daemon
2020-01-21 15:52 ` sylvain.bertrand
2020-01-21 15:53 ` bugzilla-daemon
2020-01-21 16:00 ` bugzilla-daemon
2020-01-21 18:09 ` sylvain.bertrand
2020-01-21 18:10 ` bugzilla-daemon
2020-01-22 18:22 ` bugzilla-daemon
2020-01-22 22:05 ` bugzilla-daemon
2020-01-22 23:34 ` sylvain.bertrand
2020-01-22 23:35 ` bugzilla-daemon
2020-01-22 23:56 ` sylvain.bertrand
2020-01-22 23:57 ` bugzilla-daemon
2020-01-23 0:20 ` bugzilla-daemon
2020-01-23 0:25 ` sylvain.bertrand
2020-01-23 0:25 ` bugzilla-daemon
2020-01-23 9:06 ` bugzilla-daemon
2020-01-23 15:22 ` sylvain.bertrand
2020-01-23 15:22 ` bugzilla-daemon
2020-01-23 16:41 ` bugzilla-daemon
2020-01-23 21:21 ` bugzilla-daemon
2020-01-23 21:40 ` sylvain.bertrand
2020-01-23 21:41 ` bugzilla-daemon
2020-01-23 22:05 ` bugzilla-daemon
2020-01-23 22:52 ` sylvain.bertrand
2020-01-23 22:33 ` bugzilla-daemon
2020-01-23 22:53 ` bugzilla-daemon
2020-01-24 14:17 ` bugzilla-daemon
2020-01-24 14:52 ` sylvain.bertrand
2020-01-24 14:52 ` bugzilla-daemon
2020-01-24 16:02 ` bugzilla-daemon
2020-01-24 16:18 ` sylvain.bertrand
2020-01-24 16:19 ` bugzilla-daemon
2020-01-24 21:24 ` bugzilla-daemon
2020-01-24 21:46 ` sylvain.bertrand
2020-01-24 21:47 ` bugzilla-daemon
2020-01-26 19:04 ` sylvain.bertrand
2020-01-26 19:05 ` 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=20200118213141.GA1027@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.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.