I don’t, and can’t, debate that as it is intuitively obvious.
What I am having difficulty understanding is the idea that running the system maxed-out, 100% of the time, is “sweet”.
Going back to my example:
-
You’re wandering around in un-dramatic and easily rendered scenery, (photogrammetric or otherwise), flying along fat, dumb, and happy with your system running balls to the wall, at 100% CPU/GPU utilization.
-
You then run into an intricate aerobatic manouver, a bit of scenery that’s considerably more complex, or some combination of the two that requires additional resources. (Remember, you’re already at max utilization.)
What happens then?
Where do the additional resources come from and/or what gets sacrificed to meet the additional resource load?
Please explain what I am not understanding about how what appears to be resource starving a system is “sweet”?
I am not trying to bust chops, I am really interested in understanding how you’re getting this to work as it seems to be magic to me.