From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101978] [bisected] war thunder performance reduced by ~28%
Date: Thu, 01 Feb 2018 21:32:01 +0000 [thread overview]
Message-ID: <bug-101978-502-ZuoBNUFGJW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101978-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 593 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101978
--- Comment #9 from Konstantin A. Lepikhov <lakostis@altlinux.org> ---
BTW running warthunder under brand new 4.15 kernel + latest amd-staging-4.15
gives 25-30+ FPS and the same during the gameplay with performance set to
'auto' and fps spikes up to 50+ with 'high' performance on my R9 Fury.
But it seems that 4.15 vanilla kernel doesn't have any patches from staging
which improve performance so the results are nearly the same as it was with
4.14.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1390 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 prev parent reply other threads:[~2018-02-01 21:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 5:14 [Bug 101978] [bisected] war thunder performance reduced by ~28% bugzilla-daemon
2017-08-01 1:11 ` 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 [this message]
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-ZuoBNUFGJW@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).