From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98239] saints row 3: performance is limited by flushes
Date: Sat, 10 Dec 2016 00:44:34 +0000 [thread overview]
Message-ID: <bug-98239-502-RpnzzowlyA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98239-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 767 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98239
--- Comment #7 from almos <aaalmosss@gmail.com> ---
(In reply to Marek Olšák from comment #6)
> Doom 3 is limited by the CPU. OpenGL multithreading should help with that.
> With stock Mesa, there is no way make Doom 3 faster.
>
> When the GPU load is low, it means the app is CPU-bound. Multithreading is
> the only thing that can help with that.
Hmm, you're right. By default all cores are used 30%, but if I start doom3 with
taskset -c 0, it uses 100% of core 0, and I get 35-50fps at 6-8% gpu load. I
didn't know tasks were being moved between CPU cores this much. And it seems
that my CPU is slower than I thought.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1619 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-10 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 21:59 [Bug 98239] saints row 3: performance is limited by flushes bugzilla-daemon
2016-11-25 11:14 ` bugzilla-daemon
2016-11-25 20:06 ` bugzilla-daemon
2016-11-26 13:51 ` bugzilla-daemon
2016-12-09 19:08 ` bugzilla-daemon
2016-12-09 19:11 ` bugzilla-daemon
2016-12-09 19:24 ` bugzilla-daemon
2016-12-10 0:44 ` bugzilla-daemon [this message]
2017-03-12 13:24 ` bugzilla-daemon
2017-07-26 20:45 ` bugzilla-daemon
2017-07-26 21:31 ` 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-98239-502-RpnzzowlyA@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.