Compare any two graphics cards:
VS

GeForce GT 310 vs Radeon R5 M230

Intro

The GeForce GT 310 has a core clock speed of 589 MHz and a DDR2 memory speed of 1000 MHz. It also features a 64-bit memory bus, and makes use of a 40 nm design. It is comprised of 16 SPUs, 8 TAUs, and 4 ROPs.

Compare those specifications to the Radeon R5 M230, which features core clock speeds of 780 MHz on the GPU, and 1000 MHz on the 2048 MB of DDR3 memory. It features 320 SPUs along with 20 TAUs and 4 Rasterization Operator Units.

Display Graphs

Hide Graphs

Power Usage and Theoretical Benchmarks

Memory Bandwidth

Both cards have exactly the same memory bandwidth, so in theory they should perform the same. (explain)

Texel Rate

The Radeon R5 M230 should be quite a bit (about 231%) better at anisotropic filtering than the GeForce GT 310. (explain)

Radeon R5 M230 15600 Mtexels/sec
GeForce GT 310 4712 Mtexels/sec
Difference: 10888 (231%)

Pixel Rate

If using high levels of AA is important to you, then the Radeon R5 M230 is superior to the GeForce GT 310, by a large margin. (explain)

Radeon R5 M230 3120 Mpixels/sec
GeForce GT 310 2356 Mpixels/sec
Difference: 764 (32%)

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

Display Prices

Hide Prices

GeForce GT 310

Amazon.com

Check prices at:

Radeon R5 M230

Amazon.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

Display Specifications

Hide Specifications

Model GeForce GT 310 Radeon R5 M230
Manufacturer nVidia AMD
Year November 2009 2014
Code Name GT218 Jet Pro
Memory 512 MB 2048 MB
Core Speed 589 MHz 780 MHz
Memory Speed 2000 MHz 2000 MHz
Power (Max TDP) 31 watts (Unknown) watts
Bandwidth 16000 MB/sec 16000 MB/sec
Texel Rate 4712 Mtexels/sec 15600 Mtexels/sec
Pixel Rate 2356 Mpixels/sec 3120 Mpixels/sec
Unified Shaders 16 320
Texture Mapping Units 8 20
Render Output Units 4 4
Bus Type DDR2 DDR3
Bus Width 64-bit 64-bit
Fab Process 40 nm 28 nm
Transistors 260 million (Unknown) million
Bus PCIe 2.0 PCIe 3.0 x8
DirectX Version DirectX 10.1 DirectX 11.2
OpenGL Version OpenGL 3.1 OpenGL 4.3

Memory Bandwidth: Memory bandwidth is the maximum amount of information (in units of MB per second) that can be transferred past the external memory interface in one second. It is worked out by multiplying the card's interface width by its memory speed. If it uses 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, HDR and higher screen resolutions.

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

Pixel Rate: Pixel rate is the maximum number of pixels the graphics card can possibly record to its local memory in one second - measured in millions of pixels per second. The figure is worked out by multiplying the number of colour ROPs by the the core clock speed. ROPs (Raster Operations Pipelines - sometimes also referred to as Render Output Units) are responsible for outputting the pixels (image) to the screen. The actual pixel rate is also dependant on quite a few other factors, most notably the memory bandwidth - the lower the memory bandwidth is, the lower the potential to get to the max fill rate.

Display Prices

Hide Prices

GeForce GT 310

Amazon.com

Check prices at:

Radeon R5 M230

Amazon.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

Be the first to leave a comment!

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


*

WordPress Anti Spam by WP-SpamShield