| Priority | medium |
|---|---|
| Bug ID | 83012 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | horrible performance with vblank_mode=1 which is the default |
| Severity | normal |
| Classification | Unclassified |
| OS | All |
| Reporter | aaalmosss@gmail.com |
| Hardware | Other |
| Status | NEW |
| Version | unspecified |
| Component | Drivers/Gallium/r600 |
| Product | Mesa |
For example, Unigine Tropics benchmark gives 20fps, but with vblank_mode=0 it's 54fps. Games that don't turn off vsync by themselves suffer from this as well.
| What | Removed | Added |
|---|---|---|
| Summary | horrible performance with vblank_mode=3D1 which is the defau= lt | Unigine Tropics horrible performance with vblank_mode=3D2 (w= hich is the default) or =3D3 |
(In reply to comment #0= ) > For example, Unigine Tropics benchmark gives 20f= ps, but with vblank_mode=3D0 > it's 54fps. I can only reproduce this with vblank_mode=3D2 or =3D3, though AFAICT the d= efault is 2. > Games that don't turn off vsync by themselves su= ffer from this as well. Actually, as long as the game can sustain at least 60 fps (or whatever the display refresh rate is) with vblank_mode < 2, it should still get 60 fp= s with vblank_mode >=3D 2, and IME that's indeed the case with a lot of games. The issue with Tropics is that it can only sustain just below 60 fps, which becomes 30 fps (half the refresh rate, since it misses every other vertical blank period) with sync-to-vblank, and then there are some scenes where it drops even lower. We will hopefully be able to handle this better with DRI3/Present.
Thanks for the clarification about vblank_mode. With the default vblank settings Tropics always stays in the range of 15-25 fps.
Why don't we disable vsync by default? I think that's what pro= prietary drivers do.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/521.