Yes it is... the GPU renders the scene, shades the pixels, yada yada, at the same time the CPU is calculuting the physics for the next frame, if the GPU finishes first it waits. If the CPU finishes first, it must wait for the GPU before it can do the next frame. One will limit the other depending on who finishes first. Period.Yes! This is very easy. But you don’t seem to understand? If you think it is like the weakest link in a chain isn’t right.
The sample you gave about hous, lumber and nails. That sample is a parallel situation. This situation isn’t like the gpu.
This is why, in the 4870X2 Intel is faster, the GPU is so fast that it is now waiting on the CPU most all the time, hence, when CPUs change frequency (gets faster or slower) you see a response in the frame rate. On weaker GPUs, the CPU finishes first, waits on the GPU .. the GPU determines frame rate. So when the CPU clock varies, there is no systematic change in frame rate:
this is classic CPU limited behavior. Notice how the FPS repsonds with CPU speed using a 4870 X2 at 1920x1200 full AA.
http://www.legionhardware.com/document.php?id=770&p=7
This is classic GPU limited behavior. using the much slower 4870 (non-X2) at a meager 1600x1200 full AA. Notice, how FPS does not change with clock speed or type of CPU. This is demonstrating a GPU limited regime.
http://www.firingsquad.com/hardware/...view/page9.asp
No ... this is insane, you don't understand what a bottleneck is.... this is your problem.Originally Posted by gosh
Lumber company can supply enough lumber to build the a house in a week.
The nail company can supply enough nails to build 1 house per day.
Day 1.... enough nails arrive to build the house, some lumber arrives. Day 2, day 3, day 4.... day 7 the total lumber arrives. Fastest the house builder can build houses is 1 per week, the nail company is not the RATE LIMITER, the lumber company is... just
Bookmarks