June 3rd, 2010

Zotac GeForce GTX 465 Review @ AnandTech

NVIDIA's GeForce GTX 465: Cheaper Isn’t Always Better - AnandTech :: Your Source for Hardware Analysis and News

In recent years it’s become customary to have 3-4 high-end cards on the market at the same time using the same GPU. For the GTX 200 series we had the GTX 260, GTX 275, and GTX 285, while for the Radeon HD 5000 series we have the 5830, 5850, and 5870. With the launch of NVIDIA’s GTX 400 series last month NVIDIA filled in the first 2 spots in their lineup with the GTX 480 and GTX 470, with obvious room to grow out the family in the future.

Above the GTX 480 is of course the “full” GF100 with all of its functional units enabled, and which is still missing in action on both the consumer and HPC markets. However there’s also room for a card below the $350 GTX 470, particularly with AMD being the sole inhabitant of the “bargain” high-end $300 point. NVIDIA is to the point in the Fermi rollout where they want a piece of that market, and they have a stash of further-binned so-so GF100 chips they want to fill it with. This brings us to today, and the launch of the GeForce GTX 465.

In a nutshell, if you take a GTX 470 and disable some additional functional units, additional memory controllers, and additional ROPs, while turning down the memory speed any further, you get the GTX 465. NVIDIA has shut off another 3 Streaming Multiprocessors (SMs) from GF100, leaving the GTX 465 with 11 of them, giving it a total of 352 CUDA Cores/SPs, and 44 texture units. Meanwhile the ROPs have been cut down to 32 ROPs, and another memory controller disabled, making for a 256-bit memory bus attached to 1GB of 802MHz (3208MHz effective) GDDR5. All told the GTX 465 has around 78% of the texture/shader power of the GTX 470, 80% the ROP power, 76% of the memory bandwidth of the GTX 470, and 80% of the memory capacity. The loss of 256MB of RAM will be particularly interesting, as it means NVIDIA has surrendered its memory capacity advantage over AMD’s reference cards – both are even at 1GB.

(…)