Review Roundup november 11 2010


anandtech reviewed the NVIDIA GeForce GTX 580

So what makes GTX 580 faster? We’ll start with the obvious: it’s a complete chip. All the L2 cache, all the ROPs, all the SMs, it’s all enabled. When it comes to gaming this is as fast as GF110 can be, and it’s only through NVIDIA’s artificial FP64 limitations that double-precision computing isn’t equally unrestricted.

As for FurMark, due to NVIDIA’s power throttling we’ve had to get a bit creative. FurMark is throttled to the point where the GTX 580 registers 360W, thanks to a roughly 40% reduction in performance under FurMark.

Much more likely is a 3GB GTX 580, seeing as how NVIDIA’s official product literature calls the GTX 580 the “GeForce GTX 580 1.5GB”, a distinction that was never made for the GTX 480.

Meanwhile the AMD camp is gearing up for their own launches. The 6900 series is due to launch before the year is out, bringing with it AMD’s new Cayman GPU.


bjorn3dtested the NVIDIA GeForce GTX 580

The Nvidia GeForce GTX 580 also comes with 512 CUDA cores, but this time all 512 cores are exposed and fully functional. There are more cores available for rendering data, and there is an extra PolyMorph Engine for better tessellation. The new improved and optimized chip is now known as the GF110.

Overclocking the GTX 580 was a snap, but its full overclocking potential is not yet possible as the current overclocking tools still do not have the capability to change voltages.

The maximum we could get was 836MHz on the GPU clock speed, 1112MHz on the Memory, and 1672MHz on the Shader.

Both the 512 CUDA cores and the 16 PolyMorph rendering units provide excellent performance increase in today’s DX11 games in tessellation and other 3D rendering. The GTX 580 also offers higher clock frequencies for the GPU, Shader clock, and memory clock frequencies, allowing the gamers to squeeze even more performance out of the GPU during gaming on high resolutions and graphics settings.


guru3d reviewed the NVIDIA GeForce GTX 580

The GTX 580 has the full 512 shader processors activated, meaning a notch more performance just based on that alone already. So that’s 512 shader processors, 32 more than the GTX 480 had.

Though still a 40nm based chip, the GF110 GPU comes with almost 3 billion transistors embedded into it. The TDP remains the same at roughly 240~250 Watts, while performance goes up ~20%.

Saying that the GeForce GTX 580 is merely a respin product would not do NVIDIA justice, this certainly is a new taped out revision that has been tweaked and made more efficient. The end result is a card that is something we expected early 2010, but is faster.


hardocptested the NVIDIA GeForce GTX 580

NVIDIA has a new adaptive fan speed control that has smoothed out the transitions in fan speed. Meaning, there won’t be as hard of a ramp up in fan speed and ramp down in fan speed, so you won’t notice the transition in fan speeds. RPM ramp up is nice and smooth. This optimized fan controller is another method for balancing acoustics and temperatures.

The big thing is that all 512 CUDA cores are active, compared to 480 in the GTX 480. This allows better shader and geometry performance straight out of the gate.

The GeForce GTX 580 undoubtedly leaves us with the feeling that it is what the GeForce GTX 480 should have been. Our gameplay performance along with the GTX 580’s sound and heat profiles have shown us what NVIDIA truly wanted for the GTX 480 back in March. In all games, the GeForce GTX 580 is a significantly better performing video card than the Radeon HD 5870.

Advertisements

~ by benchmarkstest on November 11, 2010.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: