Queued frame causes choppy graphics performance

I used to encounter choppy videos for a similar reason: I didn't understand the underlying knowledge of the video card at the time. I saw a maskframexxx interface at the underlying layer of the engine, which was used to modify the underlying registration information of the video card using the registry, at that time, it was still a client code farmer's thinking that fell into the interface habits. Instead of understanding the underlying meaning, I accidentally changed it to 30. So the game starts to get stuck every few minutes. During the debugging process, we used the great CPU choppy profile tool, GPU tool perfhud, and so on. Finally, I found this problem with the wisdom of the boss, so I kept this point in mind. Queued FrameThis generally limits GPU to not lag behind the CPU (render thread) by more than one frame, but it does not seem to be the best strategy here. If it is possible to lag behind by up to three frames, it provides better fault tolerance for GPU time instability. That is, it will be smoother. Many touch-based games can try to make such changes. However, the side effects are obvious. For example, the occlusion query will be much later. After reading DX documents, frame lags behind API: idirect3ddevice9ex: setmaximumframelatencyidxgidevice1: setmaximumframelatency