From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101769] 2X performance regression on Mesa 17.1 vs 17.0
Date: Wed, 12 Jul 2017 20:35:59 +0000 [thread overview]
Message-ID: <bug-101769-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2876 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101769
Bug ID: 101769
Summary: 2X performance regression on Mesa 17.1 vs 17.0
Product: Mesa
Version: 17.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: david@lunarg.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 132646
--> https://bugs.freedesktop.org/attachment.cgi?id=132646&action=edit
hack to apitrace for duplicating problem
We have an internal OpenGL benchmarking tool that measures the performance of
certain frames in apitrace files. We have been using this tool to measure
the performance of various releases of Mesa.
We recently found a large regression in Mesa performance of Half Life Episode
2, as measured by our benchmarking tool. We measured the following frame rates
when running the benchmark with Mesa built from the listed source tags:
tag mesa-17.0.0 358.6 fps
tag mesa-17.1.3 151.1 fps
This is a reduction in performance of more than 2X.
Since the tool we use to measure performance is an internal tool and we cannot
distribute it, I hacked apitrace to behave similar to our tool so that apitrace
can be used to measure the performance of the problem frame. The frame rates I
measured with this hacked apitrace benchmark are:
tag mesa-17.0.0 417.7 fps
commit 071d80b 393.9 fps
commit f81ede4 324.6 fps
tag mesa-17.1.3 196.0 fps
The hacked apitrace shows about the same performance drop between mesa-17.0.0
and mesa-17.1.3 as our original benchmark. I also include the results for
commits 071d80b and f81ede4 because commit f81ede4 seemed to show the single
largest performance drop of all commits between mesa-17.0.0 and mesa-17.1.3.
The configuration of the system I have been using to measure Mesa performance
is:
CPU: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
RAM: 16Gb
GPU: AMD RX480
Attached is the patch I applied to apitrace to create my hacked apitrace that
attempts to duplicate the original benchmark.
After building apitrace with the above patch, I used the following command to
measure performance:
vblank_mode=0 glretrace -b hl2_linux.trace
I can make the hl2_linux.trace trace file available on request. We cannot
widely distribute it because it contains Valve IP (i.e. game images). Please
send a request directly to david@lunarg.com.
Note that we have observed similar performance drops for other games, but I
have concentrated on isolating and reporting on one frame in one game for now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4555 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-12 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 20:35 bugzilla-daemon [this message]
2017-09-01 21:00 ` [Bug 101769] 2X performance regression on Mesa 17.1 vs 17.0 bugzilla-daemon
2017-09-01 22:21 ` bugzilla-daemon
2019-05-07 0:45 ` bugzilla-daemon
2019-09-25 17:59 ` 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-101769-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).