[Mesa-dev] Problem with RX 480 on Alien: Isolation and Dota 2

[Marek Olšák]

Those are just memory management stats. Linux 4.9 will contain
optimizations that should prevent such fps drops.

Marek

On Sep 24, 2016 2:23 AM, "Romain Failliot" <romain.failliot at foolstep.com>
wrote:

> So I've activated a bunch of stuff: GALLIUM_HUD="num-compilations,
> num-bytes-moved,num-evictions;fps,cpu;draw-calls,VRAM-usage" and had one
> small freeze of around 2s.
> Here is the screenshot (look at the fps drop and the concurrent num bytes
> moved and num evictions):
>
> https://framapic.org/GSwpilewir6u/BehgZbtf7axl.png
>
> I'm not sure what these two properties mean... does it speak to you? Do
> you think I should show any another property?
> BTW I saw that I was pushing my GPU a bit too much as I was around 20 fps,
> maybe that's the problem. I thought that the RX 480 was able to handle this
> game with medium video options.
>
> In the meantime I'll play more and try to get more screenshots of these
> kind of situations.
>
> Thanks!
>
> 2016-09-23 18:21 GMT-04:00 Romain Failliot <romain.failliot at foolstep.com>:
>
>> Thanks Marek, I'll test that!
>>
>> In the meantime, firstly I fixed an important bug in Mesamatrix so now
>> the matrix is more accurate, and I also just found the problem with Dota 2:
>> it is not because of the new drivers but because of a change I did in the
>> video options, I don't remember having done that but it was apparently in
>> borderless window mode which GNOME doesn't handle very well apparently.
>>
>> Now that this is solved, I'll try to understand what's happening with
>> Alien: Isolation.
>>
>> Thanks!
>>
>> 2016-09-21 7:36 GMT-04:00 Marek Olšák <maraeo at gmail.com>:
>>
>>> You can use the GALLIUM_HUD environment variable to find out the cause
>>> of those hiccups. Just set it before running steam. Type
>>> "GALLIUM_HUD=help glxgears" - that should print the available options.
>>>
>>> From the top of my head, the useful graphs are:
>>> - num-evictions (TTM overhead as the number of buffers moved)
>>> - num-bytes-moved (TTM overhead as the number of bytes moved)
>>> - num-compilations (compiler invocations)
>>>
>>> There are also a bunch of useful things like various VRAM and GTT
>>> usage stats, GPU-load, etc.
>>>
>>> Marek
>>>
>>> On Tue, Sep 20, 2016 at 1:25 AM, Romain Failliot
>>> <romain.failliot at foolstep.com> wrote:
>>> > 2016-09-19 18:40 GMT-04:00 Marek Olšák <maraeo at gmail.com>:
>>> >> Do you mean the PC is frozen for 2 minutes or just occasional hiccups
>>> >> for 2 minutes?
>>> >
>>> > Occasional hiccups for 2 minutes. The game works well, I wander around
>>> > and, from time to time, it freezes for a random duration between 2
>>> > seconds and 2 minutes (on average I'd say it's 30 seconds) and then
>>> > the game continues like nothing happened (the sound still works during
>>> > the freeze though).
>>> >
>>> > I played yesterday for instance and I had 10 minutes without any
>>> > freeze and then 2 freezes in less than a minute. It's really random,
>>> > but it seems to be related to the new places I visit, once I had one
>>> > or more freezes in an area, I won't have the freeze a freeze in this
>>> > area anymore. That's why I think it could be linked to shader
>>> > compilation.
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160924/00c978d2/attachment.html>