Split Graphics Jobs (Vulkan)
The following is intended for informational purposes only, and may not be incorporated into any contract. No purchasing decisions should be made based on the following materials. Unity is not committing to deliver any functionality, features or code. The development, timing and release of all products, functionality and features are at the sole discretion of Unity, and are subject to change.
If you have accepted to use functional cookies and logged in using your Unity ID at the top right of the page, then sharing feedback is as simple as clicking a card below, selecting a topic’s importance, adding your point of view, and submitting. If you prefer not to accept functional cookies or log in, you will be prompted to enter an email address and validate it, so we know how to reach out when the topic evolves. For more information read the Feedback and privacy terms.
Summary
Modern graphics APs such as DirectX12, Vulkan and Metal allow for better CPU utilization via multi-threaded recording and submission of command buffers (graphics API calls), thus optimizing the CPU rendering setup. 'Graphics Jobs' can be enabled in the Player Settings in order to take advantage of such functionality.
When using Native Graphics Jobs, the main thread processes and queues intermediate drawing commands, which the rendering thread converts into graphics API calls by launching worker threads that record and submit GPU command buffers to queue.
We are working on various optimizations to Graphics Jobs, most noticeably the introduction of a new threading mode. The new threading mode aims to remove unnecessary synchronization of main thread and graphics job threads at the beginning/end of frame, thus generally improving performance.
Intended Outcome / Usecase
- When using Graphics Jobs on Vulkan, a new threading mode is supported in order to improve CPU performance.