 |
 |
GeForce GTX 285 1GB vs GeForce GTX 560 Ti
Intro
The GeForce GTX 285 1GB makes use of a 55 nm design. nVidia has set the core speed at 648 MHz. The GDDR3 RAM is set to run at a speed of 1242 MHz on this particular model. It features 240 SPUs along with 80 Texture Address Units and 32 ROPs.Compare all of that to the GeForce GTX 560 Ti, which has GPU clock speed of 822 MHz, and 1024 MB of GDDR5 RAM running at 1002 MHz through a 256-bit bus. It also is comprised of 384 Stream Processors, 64 TAUs, and 32 Raster Operation Units.
Power Usage and Theoretical Benchmarks
Power Consumption (Max TDP)
| GeForce GTX 560 Ti |
|
170 Watts |
| GeForce GTX 285 1GB |
|
204 Watts |
|
|
Memory Bandwidth
Performance-wise, the GeForce GTX 285 1GB should in theory be much better than the GeForce GTX 560 Ti in general. (explain)
| GeForce GTX 285 1GB |
|
158976 MB/sec |
| GeForce GTX 560 Ti |
|
128256 MB/sec |
|
|
Texel Rate
The GeForce GTX 560 Ti should be a small bit (more or less 1%) better at anisotropic filtering than the GeForce GTX 285 1GB. (explain)| GeForce GTX 560 Ti |
|
52608 Mtexels/sec |
| GeForce GTX 285 1GB |
|
51840 Mtexels/sec |
|
|
Pixel Rate
If using lots of anti-aliasing is important to you, then the GeForce GTX 560 Ti is the winner, by far. (explain)| GeForce GTX 560 Ti |
|
26304 Mpixels/sec |
| GeForce GTX 285 1GB |
|
20736 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
GeForce GTX 285 1GBAmazon.com
Check prices at:
|
GeForce GTX 560 TiAmazon.com
Check prices at:
|
Please note that the price comparisons are based on search keywords - sometimes it might show cards with very similar names that are not exactly the same as the one chosen in the comparison. We do try to filter out the wrong results as best we can, though.
Specifications
| Model | GeForce GTX 285 1GB | GeForce GTX 560 Ti |
|---|---|---|
| Manufacturer | nVidia | nVidia |
| Year | January 15, 2009 | January 2011 |
| Code Name | G200b | GF114 |
| Memory | 1024 MB | 1024 MB |
| Core Speed | 648 MHz | 822 MHz |
| Memory Speed | 2484 MHz | 4008 MHz |
| Power (Max TDP) | 204 watts | 170 watts |
| Bandwidth | 158976 MB/sec | 128256 MB/sec |
| Texel Rate | 51840 Mtexels/sec | 52608 Mtexels/sec |
| Pixel Rate | 20736 Mpixels/sec | 26304 Mpixels/sec |
| Unified Shaders | 240 | 384 |
| Texture Mapping Units | 80 | 64 |
| Render Output Units | 32 | 32 |
| Bus Type | GDDR3 | GDDR5 |
| Bus Width | 512-bit | 256-bit |
| Fab Process | 55 nm | 40 nm |
| Transistors | 1400 million | 1950 million |
| Bus | PCIe x16 2.0 | PCIe x16 |
| DirectX Version | DirectX 10 | DirectX 11 |
| OpenGL Version | OpenGL 3.1 | OpenGL 4.1 |
Memory Bandwidth: Bandwidth is the largest amount of information (measured in megabytes per second) that can be transferred past the external memory interface in one second. The number is worked out by multiplying the card's interface width by the speed of its memory. If the card has DDR type RAM, it must be multiplied by 2 again. If it uses DDR5, multiply by 4 instead. The better the bandwidth is, the faster the card will be in general. It especially helps with AA, High Dynamic Range and high resolutions.
Texel Rate: Texel rate is the maximum number of texture map elements (texels) that are applied in one second. This figure is worked out by multiplying the total number of texture units by the core speed of the chip. The higher the texel rate, the better the graphics card will be at texture filtering (anisotropic filtering - AF). It is measured in millions of texels processed in a second.
Pixel Rate: Pixel rate is the maximum number of pixels that the graphics chip can possibly record to the local memory per second - measured in millions of pixels per second. The number is calculated by multiplying the amount of ROPs by the the core clock speed. ROPs (Raster Operations Pipelines - also called Render Output Units) are responsible for outputting the pixels (image) to the screen. The actual pixel output rate also depends on lots of other factors, especially the memory bandwidth of the card - the lower the bandwidth is, the lower the ability to reach the maximum fill rate.
GeForce GTX 285 1GBAmazon.com
Check prices at:
|
GeForce GTX 560 TiAmazon.com
Check prices at:
|
Please note that the price comparisons are based on search keywords - sometimes it might show cards with very similar names that are not exactly the same as the one chosen in the comparison. We do try to filter out the wrong results as best we can, though.
|
Comments
4 Responses to “GeForce GTX 285 1GB vs GeForce GTX 560 Ti”[...] choice on core number rather than just latest and greatest... you might find this interesting GeForce GTX 285 1GB vs GeForce GTX 560 Ti – Performance Comparison Benchmarks @ Hardware Compa... __________________ Apocalips Japan Blog Visit the [...]
I build my own computers for me and my family. I also build for other peaple as well for a little xtra cash. When i do my builds i reserch every main component i install.i decided to check into the 200 series video cards to se how far the 400 and 500 series have advanced.Much to my surprise i did not find much diference. It seems to me the 285 overall is better then the 560 and the 285 matches up very well against the 560 firmi.I am building 2 new machines at the moment, 1 for me 1 for my son. I plan to get a gtx 285 for mine and a 560 firmi for him. this will tell me how closly matched they are.
[...] GeForce GTX 285 1GB vs GeForce GTX 560 Ti – Performance …Feb 7, 2012 … nVidia has clocked the core speed at 648 MHz. …. the 285 overall is better then the 560 and the 285 matches up very well against the 560 firmi. [...]
Troy remember though that the 560 supports directx 11 and opengl v4 - it also performs similar if not slightly better than a 6950. It would be more efficient overall as its a newer core design. Also I hope that your son's and your computer have identical specs for everything aside from graphics... otherwise a fair comparison cannot be pulled...