AMD Radeon R7 350 vs AMD Radeon Vega 10 Mobile Comparison

AMD
RADEON

AMD Radeon R7 350

CORE STATE Cape Verde
VRAM 2 GB
CLOCK SPEED —
TDP 55 W
BUS WIDTH 128 bit
ARCHITECTURE GCN 1.0
nm
PROCESS 28 nm
LAUNCH DATE 2016
VS
AMD
RADEON

Radeon Vega 10 Mobile

CORE STATE Raven-M
VRAM System Shared
CLOCK SPEED 1301 MHz
TDP 10 W
BUS WIDTH System Shared
ARCHITECTURE GCN 5.0
nm
PROCESS 14 nm
LAUNCH DATE 2019

PERFORMANCE BENCHMARKS

geekbench_opencl
7,792
6,476
geekbench_vulkan
7,057
N/A

Analysis: AMD Radeon R7 350 vs AMD Radeon Vega 10 Mobile

FAQ

Q: Which GPU has the higher average benchmark score?

A: The AMD Radeon R7 350 records an average benchmark score of 7425, placing it in the 40th percentile of all GPUs in the database. The AMD Radeon Vega 10 Mobile averages 6476, sitting in the 37th percentile. The R7 350 leads by roughly 950 points.

Q: How does the R7 350 compare to its nearest rivals?

A: The R7 350 sits within a very tight cluster. It trails the Intel UHD Graphics 750 by 0.2%, the AMD Radeon HD 8850M by 0.3%, and the NVIDIA GeForce GTX 1650 by 0.6%. It is 1.7% behind the Intel Arc A310. These deltas are all under two percent, indicating near-identical average performance.

Q: How does the Vega 10 Mobile compare to its nearest rivals?

A: The Vega 10 Mobile is 0.1% behind the NVIDIA Quadro M5000M and 0.3% behind the NVIDIA GeForce GT 555M. It trails the NVIDIA GeForce GTX 670M by 0.6%. Interestingly, it is 1.1% ahead of the NVIDIA RTX PRO 5000 72 GB Blackwell, a much higher-tier card in the database.

Q: What is the direct benchmark result between these two GPUs?

A: In the Geekbench OpenCL test, the R7 350 scores 7792 against the Vega 10 Mobile's 6476. This gives the R7 350 a 20.3% advantage in that specific workload.

Q: What process nodes do these GPUs use?

A: The R7 350 is built on TSMC's 28 nm process and contains 1,500 million transistors on a 123 mm² die. The Vega 10 Mobile uses GlobalFoundries' 14 nm process, packing 4,940 million transistors into a 210 mm² die.

Q: Do both GPUs support the same DirectX version?

A: Both support DirectX 12, but with different feature levels. The R7 350 supports DirectX 12 (11_1), while the Vega 10 Mobile supports DirectX 12 (12_1). Both GPUs support OpenGL 4.6, while Vulkan support differs: the R7 350 supports Vulkan 1.2.170, and the Vega 10 Mobile supports Vulkan 1.3.

Architecture Differences

The AMD Radeon R7 350 is built on the GCN 1.0 architecture using the Cape Verde chip, belonging to the Pirate Islands (R7 300) generation. The AMD Radeon Vega 10 Mobile uses the GCN 5.0 architecture with the Raven-M chip, part of the Vega IGP (Raven Ridge-M) generation. These are two distinct architectural eras within AMD's lineup.

The manufacturing processes differ substantially. The R7 350 uses a 28 nm process from TSMC, with 1,500 million transistors on a 123 mm² die, giving a transistor density of 12.2M per mm². The Vega 10 Mobile is fabricated on a 14 nm process from GlobalFoundries, containing 4,940 million transistors on a 210 mm² die, for a density of 23.5M per mm². The newer process allows nearly double the transistor density despite the larger physical die.

Compute resources are configured differently. The R7 350 has 512 shading units, 32 texture mapping units, and 16 raster operation pipelines. The Vega 10 Mobile has 640 shading units, 40 TMUs, but only 8 ROPs. The Vega part has more shading and texturing hardware but half the ROP count.

Memory architecture is a fundamental split. The R7 350 is a discrete card with 2 GB of GDDR5 memory on a 128-bit bus, delivering 72.00 GB/s of bandwidth. The Vega 10 Mobile is an integrated GPU with system-shared memory; its bus width and bandwidth are system dependent, so no fixed figures exist.

Clock behavior also differs. The R7 350 lists only a memory clock of 1125 MHz (4.5 Gbps effective) with no base or boost figures recorded. The Vega 10 Mobile records a base clock of 300 MHz and a boost clock of 1301 MHz.

The R7 350 is a single-slot card with no power connectors, a 55 W TDP, and a suggested PSU of 250 W. The Vega 10 Mobile is an IGP with a 10 W TDP, no power connectors, and no suggested PSU. The R7 350 connects via PCIe 3.0 x16, while the Vega 10 Mobile uses an integrated IGP bus interface. Display outputs on the R7 350 include 1x DVI, 1x HDMI 1.4a, and 1x DisplayPort 1.2; the Vega 10 Mobile's outputs are portable-device dependent.

The Verdict

The data points to a clear but workload-dependent choice. The R7 350 holds a 20.3% lead in the only head-to-head benchmark recorded, Geekbench OpenCL, and carries a higher average score of 7425 versus 6476. For users who need a discrete desktop solution with fixed memory bandwidth and established display outputs, the R7 350 is the stronger performer in the measured workload.

The Vega 10 Mobile, however, belongs to a different class entirely. It is an integrated part of a mobile platform, drawing only 10 W against the R7 350's 55 W. It offers more shading units and TMUs, a higher boost clock of 1301 MHz, and newer API support with DirectX 12 (12_1) and Vulkan 1.3. Its performance is system dependent because memory is shared with the host.

For raw compute in the recorded benchmark, the R7 350 wins. For a low-power integrated solution with modern API support, the Vega 10 Mobile is the relevant choice. The R7 350 is end-of-life as a discrete product, and the Vega 10 Mobile is also end-of-life, but they serve different markets: desktop add-in cards versus mobile systems.

Specification Differences

| Specification | AMD Radeon R7 350 | AMD Radeon Vega 10 Mobile |

|---|---|---|

| Architecture | GCN 1.0 | GCN 5.0 |

| Chip | Cape Verde | Raven-M |

| Generation | Pirate Islands (R7 300) | Vega IGP (Raven Ridge-M) |

| Process Node | 28 nm (TSMC) | 14 nm (GlobalFoundries) |

| Transistors | 1,500 million | 4,940 million |

| Die Size | 123 mm² | 210 mm² |

| Transistor Density | 12.2M / mm² | 23.5M / mm² |

| Base Clock | Not recorded | 300 MHz |

| Boost Clock | Not recorded | 1301 MHz |

| Memory Clock | 1125 MHz (4.5 Gbps effective) | System Shared |

| Memory Size | 2 GB GDDR5 | System Shared |

| Memory Bus | 128 bit | System Shared |

| Memory Bandwidth | 72.00 GB/s | System Dependent |

| Shading Units | 512 | 640 |

| TMUs | 32 | 40 |

| ROPs | 16 | 8 |

| Pixel Rate | 12.80 GPixel/s | 10.41 GPixel/s |

| Texture Rate | 25.60 GTexel/s | 52.04 GTexel/s |

| FP32 | 819.2 GFLOPS | 1.665 TFLOPS |

| FP16 | Not recorded | 3.331 TFLOPS (2:1) |

| TDP | 55 W | 10 W |

| Slot Width | Single-slot | IGP |

| Suggested PSU | 250 W | Not recorded |

| Bus Interface | PCIe 3.0 x16 | IGP |

| Display Outputs | 1x DVI, 1x HDMI 1.4a, 1x DisplayPort 1.2 | Portable Device Dependent |

| DirectX | 12 (11_1) | 12 (12_1) |

| Vulkan | 1.2.170 | 1.3 |

| Release Date | 2016-07-05 | 2019-01-07 |

| Length | 168 mm (6.6 inches) | Not recorded |

Head-to-Head Benchmarks

The database records a single direct comparison between these two GPUs: Geekbench OpenCL. The R7 350 scores 7792, and the Vega 10 Mobile scores 6476. The resulting delta is 20.3% in favor of the R7 350.

This is a substantial margin. A 20.3% lead in a compute-oriented workload like OpenCL indicates that the discrete R7 350's dedicated memory subsystem and higher pixel rate contribute meaningfully to real performance. The R7 350's pixel rate of 12.80 GPixel/s exceeds the Vega 10 Mobile's 10.41 GPixel/s, and its FP32 throughput of 819.2 GFLOPS is roughly half the Vega part's 1.665 TFLOPS, yet the R7 350 still wins the benchmark. This suggests the Vega 10 Mobile's higher theoretical compute is not translating into OpenCL gains, likely due to system-shared memory limitations.

The Vega 10 Mobile does hold advantages in other measured specifications. Its texture rate of 52.04 GTexel/s is more than double the R7 350's 25.60 GTexel/s. Its FP16 throughput of 3.331 TFLOPS (2:1) is not recorded for the R7 350 at all. These figures indicate the Vega architecture is more capable in certain modern workloads, even if the OpenCL test does not reflect it.

The R7 350's nearest rivals in the database include the Intel UHD Graphics 750 at 7441 (-0.2%), the AMD Radeon HD 8850M at 7447 (-0.3%), the NVIDIA GeForce GTX 1650 at 7472 (-0.6%), and the Intel Arc A310 at 7550 (-1.7%). The R7 350 is essentially at parity with all of them. The Vega 10 Mobile's nearest rivals are the NVIDIA Quadro M5000M at 6481 (-0.1%), the NVIDIA GeForce GT 555M at 6493 (-0.3%), the NVIDIA GeForce GTX 670M at 6513 (-0.6%), and the NVIDIA RTX PRO 5000 72 GB Blackwell at 6407 (+1.1%). The Vega part also sits at parity with its rivals, with all deltas under 1.1%.

Where Each One Wins

The R7 350 wins in the recorded OpenCL benchmark by 20.3%, and it holds the higher percentile rank at 40 versus 37. It also has a higher pixel rate, 12.80 GPixel/s versus 10.41 GPixel/s, and a fixed 72.00 GB/s memory bandwidth. For users running OpenCL compute workloads on a desktop, the R7 350 is the stronger choice based on the data.

The R7 350 also offers a fixed 2 GB GDDR5 frame buffer, which removes dependency on system memory performance. Its single-slot form factor and 168 mm length make it a straightforward discrete card for desktop builds. It supports PCIe 3.0 x16, giving it a dedicated bus interface.

The Vega 10 Mobile wins on efficiency. Its 10 W TDP is dramatically lower than the R7 350's 55 W, making it suitable for portable devices where power draw is constrained. It has more shading units (640 versus 512), more TMUs (40 versus 32), and a higher boost clock of 1301 MHz. Its FP32 throughput of 1.665 TFLOPS is double the R7 350's 819.2 GFLOPS, and its FP16 capability of 3.331 TFLOPS (2:1) is not available on the R7 350.

The Vega 10 Mobile also supports newer APIs. It offers DirectX 12 (12_1) versus the R7 350's DirectX 12 (11_1), and Vulkan 1.3 versus Vulkan 1. For applications that leverage newer feature levels, the Vega part is more future-proof on paper despite its lower benchmark score.

In texturing workloads, the Vega 10 Mobile's 52.04 GTexel/s is more than double the R7 350's 25.60 GTexel/s. This could matter in certain rendering scenarios that are heavy on texture sampling. The Vega 10 Mobile was released on 2019-01-07, roughly two and a half years after the R7 350's 2016-07-05 release, so the architecture is newer.

The use case split is therefore split cleanly: the R7 350 for measured OpenCL performance and desktop integration, the Vega 10 Mobile for low-power mobile platforms with higher compute and modern API support.

DETAILED SPECIFICATIONS

SPECIFICATION
R7 350
Vega 10 Mobile
Core Specs
Shading Units
512
640 +25.0%
Shaders
512
640 +25.0%
TMUs
32
40 +25.0%
ROPs
16
8 -50.0%
Compute Units
8
10 +25.0%
Clocks
Base Clock
—
300 MHz
Boost Clock
—
1301 MHz
GPU Clock
800 MHz
—
Memory Clock
1125 MHz 4.5 Gbps effective
System Shared
Memory
Memory Size
2 GB
System Shared
VRAM (MB)
2,048
—
Memory Type
GDDR5
System Shared
Memory Bus
128 bit
System Shared
Bandwidth
72.00 GB/s
System Dependent
Cache
L1 Cache
16 KB (per CU)
—
L2 Cache
256 KB
—
Performance
Pixel Rate
12.80 GPixel/s
10.41 GPixel/s
Texture Rate
25.60 GTexel/s
52.04 GTexel/s
FP32 (TFLOPS)
819.2 GFLOPS
1.665 TFLOPS
FP64 (TFLOPS)
51.20 GFLOPS (1:16)
104.1 GFLOPS (1:16)
FP16 (TFLOPS)
—
3.331 TFLOPS (2:1)
Power
TDP
55 W
10 W
TDP (W)
55
10 -81.8%
Suggested PSU
250 W
—
Power Connectors
None
None
Architecture
Architecture
GCN 1.0
GCN 5.0
GPU Name
Cape Verde
Raven-M
Generation
Pirate Islands (R7 300)
Vega IGP (Raven Ridge-M)
Process Size
28 nm
14 nm
Transistors
1,500 million
4,940 million
Die Size
123 mm²
210 mm²
Foundry
TSMC
GlobalFoundries
Density
12.2M / mm²
23.5M / mm²
API Support
DirectX
12 (11_1)
12 (12_1)
OpenGL
4.6
4.6
Vulkan
1.2.170
1.3
OpenCL
2.1 (1.2)
2.1
Shader Model
6.5 (5.1)
6.7
Physical
Slot Width
Single-slot
IGP
Length
168 mm 6.6 inches
—
Outputs
1x DVI1x HDMI 1.4a1x DisplayPort 1.2
Portable Device Dependent
Bus Interface
PCIe 3.0 x16
IGP
Other
Production
End-of-life
End-of-life
Predecessor
Volcanic Islands
GCN 3.0 IGP
Successor
Arctic Islands
Navi II IGP
View Radeon R7 350 Details View Radeon Vega 10 Mobile Details