From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107939] Commit 888b7fc causes performance regression
Date: Fri, 14 Sep 2018 15:40:36 +0000 [thread overview]
Message-ID: <bug-107939-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107939
Bug ID: 107939
Summary: Commit 888b7fc causes performance regression
Product: Mesa
Version: 18.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: david@lunarg.com
QA Contact: dri-devel@lists.freedesktop.org
Our Vulkan regression test suite includes a Vulkan trace of the Sasha Willems
shadowmapping demo. We found that the fps when playing back that trace file had
decreased by about 20%. I narrowed down the performance drop to commit
888b7fc.
I duplicated the performance drop with the demo itself. Without commit 888b7fc,
the demo runs at an average of 3125 fps. With commit 888b7fc, it runs at 2675
fps. This is a performance regression of about 14%. I ran this on a system with
an Intel i5-6600K CPU @ 3.50GHz and an AMD Radeon RX470 graphics card.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2552 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-09-14 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 15:40 bugzilla-daemon [this message]
2018-09-14 15:46 ` [Bug 107939] Commit 888b7fc causes performance regression 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-107939-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.