From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101978] [bisected] war thunder performance reduced by ~28%
Date: Mon, 31 Jul 2017 05:14:00 +0000 [thread overview]
Message-ID: <bug-101978-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1816 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101978
Bug ID: 101978
Summary: [bisected] war thunder performance reduced by ~28%
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: higuita@gmx.net
QA Contact: dri-devel@lists.freedesktop.org
Since sometime i notice that war thunder is running slower on my machine using
mesa-git, but as the game is always updating, i (wrongly) blamed some game
update.
Yet, some days ago, after a test with a steamOS, i could confirm that older
mesa versions worked faster than mesa-git, with the same game version. I
excluded the kernel version, so i have done a mesa bisect and found the (old)
commit that made war thunder lost about 28% performance on my setup (RX480 on a
A10-7850k):
commit ac6007460adaf4bb21028a3281ec622d1e43df49
Author: Marek Olšák <marek.olsak@amd.com>
Date: Wed Feb 15 19:50:15 2017 +0100
radeonsi: upload constants into VRAM instead of GTT
This lowers lgkm wait cycles by 30% on VI and normal conditions.
The might be a measurable improvement when CE is disabled (radeon)
or under L2 thrashing.
I'm running slackware64 -current, with kernel 4.12.1, LLVM 4.0.1 and the game
is free, so you can test it. For the bisect i started the game, run the CPU
benchmark (as workaround some bug where most first benchmarks are slower) and
then run the "still scene" benchmark. as is the shorter one, but all others
had performance drop.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3256 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:[~2017-07-31 5:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 5:14 bugzilla-daemon [this message]
2017-08-01 1:11 ` [Bug 101978] [bisected] war thunder performance reduced by ~28% bugzilla-daemon
2017-08-01 1:20 ` bugzilla-daemon
2017-08-14 19:43 ` bugzilla-daemon
2017-08-15 1:04 ` bugzilla-daemon
2017-09-29 0:30 ` bugzilla-daemon
2017-10-22 17:21 ` bugzilla-daemon
2017-11-14 0:55 ` bugzilla-daemon
2018-01-28 23:16 ` bugzilla-daemon
2018-02-01 21:32 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2018-09-20 5:05 ` bugzilla-daemon
2018-09-21 3:16 ` bugzilla-daemon
2018-12-08 21:38 ` bugzilla-daemon
2018-12-10 2:18 ` 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-101978-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;
as well as URLs for NNTP newsgroup(s).