Home › Per NVIDIA Nsight + Unity Profiler, a DRAW CALL …
Per NVIDIA Nsight + Unity Profiler, a DRAW CALL is expensive primarily because of which cost?
AMemory bandwidth to read the texture each call
BCPU-side state validation and command-buffer write
CGPU triangle setup and rasterization always dominant
DVertex shader execution time per vertex
Answer & Solution
Correct answer: B. CPU-side state validation and command-buffer write
NVIDIA Nsight + Unity docs: draw call overhead is mostly CPU work (state validation, command-list encoding). Batching reduces call count → CPU win.
Related questions
In rendering optimisation, BATCHING multiple draw calls into one is most effective when obIn CPU profiling, FALSE SHARING (cache-line ping-pong) between threads is best fixed by whIn rendering optimisation, FRUSTUM CULLING and OCCLUSION CULLING both skip work; the latteIn texture sampling, MIPMAPS reduce which artifact and at what storage cost?In modern GPU rendering, EARLY-Z (or 'Hi-Z') optimisation rejects fragments before which sIn GPU profiling, 'OVERDRAW' refers to which phenomenon?Per Unity Profiler docs, the Profiler's 'GC ALLOC' counter measures which?In game engine optimisation, an ECS (Entity Component System) typically organises componen