dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101978] [bisected] war thunder performance reduced by ~28%
Date: Tue, 01 Aug 2017 01:11:03 +0000	[thread overview]
Message-ID: <bug-101978-502-lWqw3ttosf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101978-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101978

--- Comment #1 from higuita@gmx.net ---
Running some of the other benchmarks, i get this:

Benchmark       good    bad     %

patrick         4082    3173    -22
plane           2001    1793    -10
tank (cpu)      1320    1094    -17
tanks           1706    1431    -16

in other benchmarks, the commit did not make much difference, specially on
planes, but on tanks it did a lot, "test drive" with the chi-nu tank (ie: as in
real game play) i get this fps reduction:

chi nu test     25      14      -44%

I also notice that the GPU load also drop mostly in the same degree, but the
sclk get a little higer with more spikes.for the "still scene", where i get
-28% performance, the gpu load drops 32% and about 330-370MHz for before the
commit, but 320-390MHz after the commit

GPU load        55      37      -32
sclk          330-370 320-380

Can a apitrace help in anyway to understand why this affects so much this game

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1859 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

  reply	other threads:[~2017-08-01  1:11 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 [this message]
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-lWqw3ttosf@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).