'Vulkan where to do computations

I am still a complete newbie at this so please treat me as someone who has 0 knowledge on this topic.

I'm currently making a vkCmdDraw call every frame with the vertexCount argument as 6 * numOfQuads, whilst binding a UBO that holds data for each quad, that will be used for computations inside the vertex shader.

Is it more efficient to do the computations outside of the shader (CPU), where I do all the computations prior to calling vkCmdDraw, or should I just stick to what I've currently got?

vulkancompute-shader


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions

In Vulkan, is it beneficial for the graphics queue family to be separate from the present queue family?

Why is a single depth buffer sufficient for this vulkan swapchain render loop?

vkQueuePresentKHR image has invalid layout if no command buffers are submitted

Vulkan: Errors when adding 3rd descriptor

Xamarin Android: Calling Invalidate() inside overridden OnDraw method

How to render Vulkan's scene to ImGui window

Vulkan right handed coordinate system become Left handed

Refreshing a Variable multiple times a frame(for a texture array in a shader)

Validation warning about SPIR-V Capability

using vkEnumerateInstanceVersion to get exact Vulkan API version

Handle multiply cameras in Vulkan

Aliasing a SSBO by binding it multiple times in the same shader

Is there any reason to use descriptor instead of device buffer address?

C# variables of class are zeroed after P/Invoke call

Does unrolling a loop affect the accuracy of the computations within?