Submit Benchmarks!

Submit SSD Benchmark
Submit GPU Benchmark

Compare any two graphics cards:
VS

GeForce GT 220 GDDR3 vs GeForce GT 320


Intro

The GeForce GT 220 GDDR3 uses a 40 nm design. nVidia has clocked the core frequency at 625 MHz. The GDDR3 RAM is set to run at a frequency of 1012 MHz on this particular card. It features 48 SPUs along with 16 TAUs and 8 ROPs.

Compare those specs to the GeForce GT 320, which has a clock frequency of 540 MHz and a GDDR3 memory frequency of 790 MHz. It also makes use of a 128-bit memory bus, and uses a 40 nm design. It is comprised of 72 SPUs, 24 TAUs, and 8 Raster Operation Units.

Display Graphs

Hide Graphs

Power Usage and Theoretical Benchmarks

Power Consumption (Max TDP)

GeForce GT 320 43 Watts
GeForce GT 220 GDDR3 58 Watts
Difference: 15 Watts (35%)

Memory Bandwidth

In theory, the GeForce GT 220 GDDR3 should be a lot faster than the GeForce GT 320 overall. (explain)

GeForce GT 220 GDDR3 32384 MB/sec
GeForce GT 320 25280 MB/sec
Difference: 7104 (28%)

Texel Rate

The GeForce GT 320 is a lot (approximately 30%) more effective at texture filtering than the GeForce GT 220 GDDR3. (explain)

GeForce GT 320 12960 Mtexels/sec
GeForce GT 220 GDDR3 10000 Mtexels/sec
Difference: 2960 (30%)

Pixel Rate

The GeForce GT 220 GDDR3 should be just a bit (more or less 16%) more effective at anti-aliasing than the GeForce GT 320, and should be able to handle higher resolutions more effectively. (explain)

GeForce GT 220 GDDR3 5000 Mpixels/sec
GeForce GT 320 4320 Mpixels/sec
Difference: 680 (16%)

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 GT 220 GDDR3

GeForce GT 320

Specifications

Display Specifications

Hide Specifications

Model GeForce GT 220 GDDR3 GeForce GT 320
Manufacturer nVidia nVidia
Year October 2009 February 2010
Code Name GT216 GT215
Memory 512 MB 1024 MB
Core Speed 625 MHz 540 MHz
Memory Speed 2024 MHz 1580 MHz
Power (Max TDP) 58 watts 43 watts
Bandwidth 32384 MB/sec 25280 MB/sec
Texel Rate 10000 Mtexels/sec 12960 Mtexels/sec
Pixel Rate 5000 Mpixels/sec 4320 Mpixels/sec
Unified Shaders 48 72
Texture Mapping Units 16 24
Render Output Units 8 8
Bus Type GDDR3 GDDR3
Bus Width 128-bit 128-bit
Fab Process 40 nm 40 nm
Transistors 486 million 727 million
Bus PCIe 2.0 PCIe x16
DirectX Version DirectX 10.1 DirectX 10.1
OpenGL Version OpenGL 3.2 OpenGL 3.3

Memory Bandwidth: Bandwidth is the maximum amount of information (measured in MB per second) that can be transferred across the external memory interface in a second. The number is calculated by multiplying the card's interface width by its memory clock speed. In the case of DDR type memory, it should be multiplied by 2 once again. If DDR5, multiply by 4 instead. The higher the card's memory bandwidth, the better the card will be in general. It especially helps with anti-aliasing, HDR and high resolutions.

Texel Rate: Texel rate is the maximum number of texture map elements (texels) that can be applied in one second. This number is calculated by multiplying the total texture units by the core clock speed of the chip. The higher this number, the better the graphics card will be at handling texture filtering (anisotropic filtering - AF). It is measured in millions of texels applied in one second.

Pixel Rate: Pixel rate is the most pixels the graphics card can possibly record to the local memory in a second - measured in millions of pixels per second. The figure is worked out by multiplying the amount of Raster Operations Pipelines by the the card's clock speed. ROPs (Raster Operations Pipelines - sometimes also referred to as Render Output Units) are responsible for drawing the pixels (image) on the screen. The actual pixel rate is also dependant on lots of other factors, especially the memory bandwidth of the card - the lower the memory bandwidth is, the lower the potential to reach the max fill rate.

GeForce GT 220 GDDR3

GeForce GT 320

Comments

Be the first to leave a comment!

Your email address will not be published. Required fields are marked *


*

WordPress Anti-Spam by WP-SpamShield


[X]
[X]