I'm currently inspecting an execution of our software through the Nsight profiler with visual studio.
I'm wondering what is the trigger for the "start" and "stop" of the ranges for the CPU
and GPU GPU 0 - G...
as highlighted in the following image, more precisely, what would trigger the switch from CPU
frame 53 to CPU
frame 54, same for GPU GPU 0
frame 53 to GPU GPU 0
frame 54:
Second question: should I care?
The 'frame' range is before and after I call the 'frame' method of the viewer in OSG.