From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108330] WarThunder game performance killed after Ryzen optimisations
Date: Thu, 11 Oct 2018 22:44:16 +0000 [thread overview]
Message-ID: <bug-108330-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1893 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108330
Bug ID: 108330
Summary: WarThunder game performance killed after Ryzen
optimisations
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: acelists@atlas.sk
QA Contact: dri-devel@lists.freedesktop.org
After the recent optimisation of radeonsi for Ryzen CPUs (apparently change in
thread management distributing them to CPU cores), the performance of the
WarThunder game dived radically.
Normally it was 40-60FPS. After the change it appears OK when in plain fields,
but when moving the vehicle into a more intensive area, where shots are fired
or other player vehicles are around, the FPS drops to 0-10 with really
noticeable freezes and stuttering. This was never the case before the change,
The GPU is Radeon RX 560 (4GB memory).
The CPU is AMD Threadripper 1920x (12 cores/24 threads) so it may be one where
the optimisations are applied. Are Threadripper CCX/core layout properly
recognized by the patch for Ryzen?
Before the patch I noticed, the speed of the game can be visibly negatively
affected if other tasks are running on the CPU. So I always run the game with
no other CPU heavy tasks running. The report is also with no other tasks. It
may be the change of thread scheduling from the patch has now invoked the
core/thread load scenario the game is sensitive to.
I run Mesa from git so I noticed this problem when it was merged.
Now running on Mesa 18.2.2 stable and the problem is not there.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3257 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
next reply other threads:[~2018-10-11 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 22:44 bugzilla-daemon [this message]
2018-10-23 16:41 ` [Bug 108330] WarThunder game performance killed after Ryzen optimisations bugzilla-daemon
2018-10-30 17:44 ` bugzilla-daemon
2018-10-30 18:05 ` bugzilla-daemon
2018-11-09 19:12 ` bugzilla-daemon
2018-11-09 19:59 ` bugzilla-daemon
2018-11-09 23:57 ` bugzilla-daemon
2018-11-13 19:33 ` bugzilla-daemon
2018-11-16 15:14 ` bugzilla-daemon
2018-11-26 6:48 ` 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-108330-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 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.