From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98996] Counter Strike: Global Offensive performance
Date: Mon, 05 Dec 2016 11:22:25 +0000 [thread overview]
Message-ID: <bug-98996-502-uuibkZBBTX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98996-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 718 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98996
--- Comment #1 from Christoph Haag <haagch@frickel.club> ---
Created attachment 128345
--> https://bugs.freedesktop.org/attachment.cgi?id=128345&action=edit
screenshot csgo gallium nine
For comparison purposes, here is a screenshot of the windows version with
gallium nine. Same hardware, same software.
Note the high GPU load (It only has large drops when you die and it plays the
"killcam" animation), higher CPU load and much smaller buffer wait times.
Valve said lower performance is expected because of their shader translation
with togl, but this seems extreme.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1649 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 prev parent reply other threads:[~2016-12-05 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 11:04 [Bug 98996] Counter Strike: Global Offensive performance bugzilla-daemon
2016-12-05 11:22 ` bugzilla-daemon [this message]
2017-03-22 16:57 ` [Bug 98996] Counter Strike: Global Offensive performance on Radeon Polaris bugzilla-daemon
2017-04-11 18:05 ` bugzilla-daemon
2017-04-12 1:43 ` bugzilla-daemon
2019-06-25 1: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-98996-502-uuibkZBBTX@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).