NVIDIA GeForce GTX 680 Review: Retaking The Performance Crown
by Ryan Smith on March 22, 2012 9:00 AM ESTCrysis: Warhead
Kicking things off as always is Crysis: Warhead. It’s no longer the toughest game in our benchmark suite, but it’s still a technically complex game that has proven to be a very consistent benchmark. Thus even four years since the release of the original Crysis, “but can it run Crysis?” is still an important question, and the answer continues to be “no.” While we’re closer than ever, full Enthusiast settings at a 60fps is still beyond the grasp of a single-GPU card.
While Crysis was a strong game for the GTX 580, the same cannot be said of the GTX 680. NVIDIA is off to a very poor start here, with the Radeon HD 7970 easily outperforming the GTX 680, and even the 7950 is tied or nearly tied with the GTX 680 depending on the resolution. On the bright side the GTX 680 does manage to outperform the GTX 580, but only by a relatively meager 17%.
Given the large gap in theoretical performance between the GTX 680 and GTX 580, as it turns out we’ve run into one of the few scenarios where the GTX 680 doesn’t improve on the GTX 580: memory bandwidth. In our overclocking results we discovered that a core overclock had almost no impact on Crysis, whereas a memory overclock improved performance by 8%, almost exactly as much as the memory overclock itself. When it comes to the latest generation of cards it appears that Crysis loves memory bandwidth, and this is something the Radeon HD 7900 series has in spades but the GTX 680 does not. Thankfully for NVIDIA not every game is like Crysis.
The minimum framerate situation is even worse for NVIDIA here, with the GTX 680 clearly falling behind the 7950, and improving on the GTX 580 by only 10%. At its worst Crysis is absolutely devouring memory bandwidth here, and that leaves the GTX 680 underprepared.
Facebook
Twitter
RSS
404 Comments
View All Comments
unphased - Saturday, July 28, 2012 - link
I'm using Precision X to OC my Gigabyte GTX 670 and I've got the Mem clock offset at +550Mhz. In the chart log it continues to run at 3557Mhz even while I am not playing any games.Is this normal? I even switched off Aero to check and it hasn't changed.
Gastec - Thursday, November 15, 2012 - link
I know I'm nobody, not like you americans who are always "somebody" or "something" but I can't just sit here and read and not react. It's enough that I have to put up with them on YouTube, why do you condone them here as well? I'm refering to the likes of Wreckage and CeriseCogburn users that are obviously payed individuals to do negative publicity, here in favor of nVidia. Is that something acceptable here? Am I too old or not "in tone" with the working of the Internet or what?Gastec - Thursday, November 15, 2012 - link
Having white american genetic traits that allow you to be a convincing how-to-become-rich-and-successful book and TV religion seller migh be a praized quality in your american lands but in my lands we know one thing, and one thing only: that 60 fps is what we want in our games, be them old or new. I don't care if the card can do 120 fps, 10 more than the 110 fps that the other brand can do. That's irrelevant. My monitor works at 60 Hz. If one card can do 55 fps MIN/100 fps MAX, I'll take it over the other one that can do 40 fps MIN/120 fps MAX anyday. So why don't you think about that and convince me to buy your card. With pictures of course.BrotherofCats - Monday, June 10, 2013 - link
I have had nothing but trouble with this card from the start. It crashes a dozen times a day, mostly when I am playing a video, but sometimes when I am using my word processor or Excel. Mostly it freezes the screen for about a minute, then come back with a pop up box that states my driver crashed and has recovered. About twice a day it does a complete crash, the two peripheral screens going white and the central screen gray, and I have to hard boot my computer to get it working again. Have asked for help on the Nvidea forums and facebook page, and none of their solutions, clean install of the driver, or using an earlier driver has worked. Saw on the facebook page that other people are having the same problem. Will probably have to scrap this expensive turkey and get something cheaper that works. Not recommended at all.