Parja
[H]F Junkie
- Joined
- Oct 4, 2002
- Messages
- 12,671
I did a clock speed experiment over the weekend on my system to really get a grip on how core, shader, and memory clocks effect GPU2 client performance.
I started with clock speeds at stock and then varied them upward and downward from stock to see their effect on the time required to finish 1% of a WU. For each setting, I let it finish about 5% and averaged the time (rounded to the nearest half second).
The results were pretty much as expected. Core and memory have a small effect on performance, but the shader clock is where the performance is (by roughly a factor of 5 over the other two clocks by percentage change). From maximum overclock to a 20% underclock, core and memory only cost about 1 additional second per percent. I don't have a Kill-A-Watt or similar to test the power consumption (yet...ordered one today...yay!), but I've got to believe the card is going to use significantly less power with those two clocks dropped that much.
With the shader overclocked 21%, time per % dropped a full 2.5 seconds (from 18.5 to 15), or almost a 20% drop in time per %. So performance changes almost linearly with the change in shader clock.
I started with clock speeds at stock and then varied them upward and downward from stock to see their effect on the time required to finish 1% of a WU. For each setting, I let it finish about 5% and averaged the time (rounded to the nearest half second).
The results were pretty much as expected. Core and memory have a small effect on performance, but the shader clock is where the performance is (by roughly a factor of 5 over the other two clocks by percentage change). From maximum overclock to a 20% underclock, core and memory only cost about 1 additional second per percent. I don't have a Kill-A-Watt or similar to test the power consumption (yet...ordered one today...yay!), but I've got to believe the card is going to use significantly less power with those two clocks dropped that much.
With the shader overclocked 21%, time per % dropped a full 2.5 seconds (from 18.5 to 15), or almost a 20% drop in time per %. So performance changes almost linearly with the change in shader clock.







