mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-15 14:18:04 +02:00
5529f15f31
Unfortunately we have to disable concurrent binning by default because it hurts performance in a number of desktop games without any case where we know it helps. There are less vertex fetch resource available in BV compared to BR, so when binning runs in BV, there are many vertices, and vertices are attribute heavy - BV has much worse performance than BR, sometimes more than 50% worse. Even with worse performance it won't be bad if concurrent binning actually overlapped with other workload in those cases, but in case of desktop games - there is almost never a chance for overlap. However it's impossible to statically find out if binning on BV would be much slower than on BR, and we also cannot statically predict if there is enough overlap (if any) to cover for the performance penalty. Given the above, I don't see a way out but to make concurrent binning opt in via `tu_allow_concurrent_binning` driconf toggle. Still allow concurrent binning in CI to catch issues early. Signed-off-by: Danylo Piliaiev <dpiliaiev@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41394> |
||
|---|---|---|
| .. | ||
| amd | ||
| android_stub | ||
| asahi | ||
| broadcom | ||
| c11 | ||
| compiler | ||
| drm-shim | ||
| egl | ||
| etnaviv | ||
| freedreno | ||
| gallium | ||
| gbm | ||
| getopt | ||
| gfxstream | ||
| glx | ||
| gtest | ||
| imagination | ||
| imgui | ||
| intel | ||
| kosmickrisp | ||
| loader | ||
| mesa | ||
| microsoft | ||
| nouveau | ||
| panfrost | ||
| poly | ||
| tool | ||
| util | ||
| virtio | ||
| vulkan | ||
| x11 | ||
| .clang-format | ||
| meson.build | ||