Project

General

Profile

Actions

Emulator Issues #11625

open

Revise the semantics of "Backend multi-threading" option

Added by kvark about 5 years ago. Updated about 5 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

This option enables command submission on a different thread. This is not a conventional multi-threading in Vulkan, and I find the option to be confusing.
A conventional model is that there are multiple threads recording work in command buffers, but then it gets submitted at some point on a queue that is also responsible for other things. Vulkan driver is not expected to do heavy lifting at submission time - it merely passes down the command buffers to the HW scheduler, conceptually speaking.

See fore more details: https://developer.nvidia.com/sites/default/files/akamai/gameworks/blog/munich/mschott_vulkan_multi_threading.pdf

Actions #1

Updated by Stenzek about 5 years ago

  • Status changed from New to Accepted

Indeed. The option really should be called "Submit command buffers on a worker thread", or something (but good luck fitting that in the dialog).

It does make a slight difference in performance, but the magnitude depends on the driver.

Actions

Also available in: Atom PDF