From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98693] Mad Max: Long lags when VRAM full
Date: Thu, 17 Nov 2016 13:37:44 +0000 [thread overview]
Message-ID: <bug-98693-502-TwUcnV93lV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98693-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 724 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98693
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Jani Kärkkäinen from comment #4)
> "The game I'm testing needs 3.4 GB of VRAM.
>
> Setups:
> Tonga - 2 GB: It's nearly unplayable, because freezes occur too often.
> Fiji - 4 GB: There is one freeze at the beginning (which is annoying
> too), after that it's smooth.
>
> So even 4 GB is not enough."
>
> Also the descriptions of the problem seem to match mine. A problem in memory
> handling?
The freeze at the beginning is most likely shader compilation. Mesa does not
have a shader cache yet.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1585 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-11-17 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 0:46 [Bug 98693] Mad Max: Long lags when VRAM full bugzilla-daemon
2016-11-16 8:46 ` bugzilla-daemon
2016-11-17 3:52 ` bugzilla-daemon
2016-11-17 5:50 ` bugzilla-daemon
2016-11-17 10:24 ` bugzilla-daemon
2016-11-17 13:37 ` bugzilla-daemon [this message]
2017-03-12 13:24 ` bugzilla-daemon
2019-07-04 2:36 ` 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-98693-502-TwUcnV93lV@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).