From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84663] high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME
Date: Fri, 10 Oct 2014 13:46:08 +0000 [thread overview]
Message-ID: <bug-84663-502-nnkZqB43lK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84663-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1120 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84663
Christoph Haag <haagch@frickel.club> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #107595|0 |1
is obsolete| |
--- Comment #8 from Christoph Haag <haagch@frickel.club> ---
Created attachment 107663
--> https://bugs.freedesktop.org/attachment.cgi?id=107663&action=edit
borderlands 2 with GALLIUM_HUD with patches and drm-next-3.18
Well, the good news is that I can confirm that the random huge pauses in
borderlands 2 and in unreal engine 4 demos with drm-next-3.18 are gone with the
patches.
If the CPU usage is all in Borderlands 2 itself and not in mesa, then maybe
I'll need to start asking around what other people's cpus are and how much cpu
time it uses. Maybe it really is some physics/internal rendering calculation
that is so slow, when I get almost 80 fps when the game is paused in the menu
or unfocussed..
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2674 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-10 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 15:19 [Bug 84663] New: high cpu usage, poor performance in Borderlands 2 with radeonsi, PRIME bugzilla-daemon
2014-10-06 8:41 ` [Bug 84663] " bugzilla-daemon
2014-10-06 11:48 ` bugzilla-daemon
2014-10-07 1:58 ` bugzilla-daemon
2014-10-07 11:04 ` bugzilla-daemon
2014-10-08 2:50 ` bugzilla-daemon
2014-10-09 7:54 ` bugzilla-daemon
2014-10-10 2:41 ` bugzilla-daemon
2014-10-10 13:46 ` bugzilla-daemon [this message]
2014-11-10 15:21 ` bugzilla-daemon
2017-03-12 11:11 ` bugzilla-daemon
2017-03-13 20:04 ` 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-84663-502-nnkZqB43lK@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