From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99995] New: Dirt showdown very low fps (~3fps) after update mesa
Date: Mon, 27 Feb 2017 23:47:59 +0000 [thread overview]
Message-ID: <bug-99995-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99995
Bug ID: 99995
Summary: Dirt showdown very low fps (~3fps) after update mesa
Product: Mesa
Version: 17.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: kevin01010-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Hi, I updated from mesa 13.0.x to 17.0 and Dirt showdown in mesa 13 has around
25 fps and with mesa 17 has about 2fps..
I tried in ArchLinux and Fedora (fedora 26 mesa builds), and is the same, mesa
13 works a lot better in this game
My computer is a i5 4690 and has a Nvidia GTX 750
Mesa 17: CPU is 1 core 100% and the rest about 10%
Mesa 13.0.4: CPU is about 15-20% all cores
Maybe mesa is taking all work to CPU?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2485 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-02-27 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 23:47 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-99995-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-02-28 0:22 ` [Bug 99995] Dirt showdown very low fps (~3fps) after update mesa bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 9:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 11:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 19:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-01 14:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-22 16:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-01 14:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-99995-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.