From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 51787] New: performance regression with llvm shader compiler in ut2004
Date: Fri, 06 Jul 2012 14:03:50 +0000 [thread overview]
Message-ID: <bug-51787-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=51787
Bug #: 51787
Summary: performance regression with llvm shader compiler in
ut2004
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: aaalmosss@gmail.com
Whenever some new geometry appears (even for weapon projectiles), the framerate
drops drastically for a short time. This is a frequent event, so the game
becomes unplayable overall.
There is also a big preformance drop with the old compiler, when several
players get gibbed at once (happens frequently on as-convoy), but with the llvm
compiler this is much worse.
I'm not an expert on this, but it seems as if a new vertex shader would be
compiled for each vertex array submitted, and the llvm compiler is an order of
magnitude slower.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-07-06 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 14:03 bugzilla-daemon [this message]
2012-07-06 15:25 ` [Bug 51787] performance regression with llvm shader compiler in ut2004 bugzilla-daemon
2012-08-02 22:04 ` bugzilla-daemon
2012-08-02 22:32 ` bugzilla-daemon
2012-11-01 18:17 ` bugzilla-daemon
2012-11-01 20:12 ` bugzilla-daemon
2013-05-06 23:26 ` bugzilla-daemon
2019-09-18 19:00 ` 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-51787-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.