 |
 |
|
|
|
GeForce GTX 580 3GB vs GeForce GTX 650
Intro
The GeForce GTX 580 3GB uses a 40 nm design. nVidia has clocked the core speed at 772 MHz. The GDDR5 RAM works at a frequency of 1002 MHz on this specific model. It features 512 SPUs along with 64 Texture Address Units and 48 ROPs.Compare those specs to the GeForce GTX 650, which comes with a GPU core clock speed of 1058 MHz, and 2048 MB of GDDR5 RAM set to run at 1250 MHz through a 128-bit bus. It also is made up of 384 SPUs, 32 TAUs, and 16 Raster Operation Units.
Power Usage and Theoretical Benchmarks
Power Consumption (Max TDP)
| GeForce GTX 650 |
|
64 Watts |
| GeForce GTX 580 3GB |
|
244 Watts |
|
|
Memory Bandwidth
Theoretically speaking, the GeForce GTX 580 3GB will be 140% quicker than the GeForce GTX 650 overall, due to its higher data rate. (explain)
| GeForce GTX 580 3GB |
|
192384 MB/sec |
| GeForce GTX 650 |
|
80000 MB/sec |
|
|
Texel Rate
The GeForce GTX 580 3GB will be much (more or less 46%) more effective at anisotropic filtering than the GeForce GTX 650. (explain)| GeForce GTX 580 3GB |
|
49408 Mtexels/sec |
| GeForce GTX 650 |
|
33856 Mtexels/sec |
|
|
Pixel Rate
The GeForce GTX 580 3GB will be a lot (about 119%) more effective at anti-aliasing than the GeForce GTX 650, and capable of handling higher resolutions more effectively. (explain)| GeForce GTX 580 3GB |
|
37056 Mpixels/sec |
| GeForce GTX 650 |
|
16928 Mpixels/sec |
|
|
Please note that the above 'benchmarks' are all just theoretical - the results were calculated based on the card's specifications, and real-world performance may (and probably will) vary at least a bit.
Price Comparison
Please note that the price comparisons are based on search keywords, and might not be the exact same card listed on this page. We have no control over the accuracy of their search results.
GeForce GTX 580 3GBAmazon.com
Other US-based stores
Amazon.co.uk
Amazon.de
Amazon.fr
|
GeForce GTX 650Amazon.com
Other US-based stores
Amazon.co.uk
Amazon.de
Amazon.fr
|
Specifications
| Model | GeForce GTX 580 3GB | GeForce GTX 650 |
|---|---|---|
| Manufacturer | nVidia | nVidia |
| Year | November 2010 | September 2012 |
| Code Name | GF110 | GK107 |
| Fab Process | 40 nm | 28 nm |
| Bus | PCIe x16 | PCIe 3.0 x16 |
| Memory | 3072 MB | 2048 MB |
| Core Speed | 772 MHz | 1058 MHz |
| Shader Speed | 1544 MHz | 1058 MHz |
| Memory Speed | 1002 MHz (4008 MHz effective) | 1250 MHz (5000 MHz effective) |
| Unified Shaders | 512 | 384 |
| Texture Mapping Units | 64 | 32 |
| Render Output Units | 48 | 16 |
| Bus Type | GDDR5 | GDDR5 |
| Bus Width | 384-bit | 128-bit |
| DirectX Version | DirectX 11 | DirectX 11.1 |
| OpenGL Version | OpenGL 4.1 | OpenGL 4.3 |
| Power (Max TDP) | 244 watts | 64 watts |
| Shader Model | 5.0 | 5.0 |
| Bandwidth | 192384 MB/sec | 80000 MB/sec |
| Texel Rate | 49408 Mtexels/sec | 33856 Mtexels/sec |
| Pixel Rate | 37056 Mpixels/sec | 16928 Mpixels/sec |
Memory Bandwidth: Memory bandwidth is the largest amount of data (measured in MB per second) that can be transported past the external memory interface in a second. It is calculated by multiplying the bus width by its memory speed. In the case of DDR type RAM, it must be multiplied by 2 again. If DDR5, multiply by ANOTHER 2x. The higher the memory bandwidth, the faster the card will be in general. It especially helps with anti-aliasing, High Dynamic Range and higher screen resolutions.
Texel Rate: Texel rate is the maximum amount of texture map elements (texels) that are processed per second. This number is calculated by multiplying the total texture units of the card by the core clock speed of the chip. The higher the texel rate, the better the video card will be at texture filtering (anisotropic filtering - AF). It is measured in millions of texels processed in one second.
Pixel Rate: Pixel rate is the most pixels the video card can possibly record to its local memory per second - measured in millions of pixels per second. The figure is calculated by multiplying the number of Raster Operations Pipelines by the the core clock speed. ROPs (Raster Operations Pipelines - aka Render Output Units) are responsible for filling the screen with pixels (the image). The actual pixel output rate is also dependant on lots of other factors, especially the memory bandwidth - the lower the bandwidth is, the lower the potential to reach the max fill rate.
Comments
Be the first to leave a comment!