boxleitnerb
Platinum Member
- Nov 1, 2011
- 2,601
- 2
- 81
I said "680". The 770 has significantly better memory speeds. Especially at these extremely high overclocks (1.3 GHz for the 780 is extreme), memory bandwidth will definitely bottleneck the faster card. In that review the 780 OC has 6.3 GHz memory, the 770 OC has 8.0 GHz memory. Besides: Does HardOCP monitor GPU clocks throughout their benchmarks? Or do they only look for a couple of seconds in the beginning and later the frequency might drop below 1.3 GHz under heavy and sustained benchmark load? There is simply no guarantee what the clocks actually are for the whole duration. You would have to disable boost completely with a mod bios or with K-boost to be absolutely sure.
Without such massive overclocking, the tendencies are clear, however:
http://www.pcgameshardware.de/Gefor...AMP-im-Test-preiswerter-Titan-Killer-1082941/
About 50% at similar clocks (1070 MHz).
https://www.computerbase.de/artikel/grafikkarten/2013/palit-geforce-gtx-780-super-jetstream-im-test/
53% at similar clocks (1080 MHz).
With the HT4U review I linked I assumed perfect scaling with overclocking, thus keeping the perfect scaling ratio between GK104 and GK110 at the same clocks. This is a reasonable assumption since every GPU scales perfectly with overclocking as long as memory bandwidth is increased accordingly. This is because the frontend is overclocked as well since it runs with core speed.
Without such massive overclocking, the tendencies are clear, however:
http://www.pcgameshardware.de/Gefor...AMP-im-Test-preiswerter-Titan-Killer-1082941/
About 50% at similar clocks (1070 MHz).
https://www.computerbase.de/artikel/grafikkarten/2013/palit-geforce-gtx-780-super-jetstream-im-test/
53% at similar clocks (1080 MHz).
With the HT4U review I linked I assumed perfect scaling with overclocking, thus keeping the perfect scaling ratio between GK104 and GK110 at the same clocks. This is a reasonable assumption since every GPU scales perfectly with overclocking as long as memory bandwidth is increased accordingly. This is because the frontend is overclocked as well since it runs with core speed.
Last edited: