AMD Radeon R5 M335 vs AMD Radeon R7 M265 Comparison
AMD Radeon R5 M335
Radeon R7 M265
PERFORMANCE BENCHMARKS
Analysis: AMD Radeon R5 M335 vs AMD Radeon R7 M265
Head-to-Head Benchmarks
The benchmark data presents a clear, if narrow, picture when the AMD Radeon R7 M265 and AMD Radeon R5 M335 are placed side by side. The sole head-to-head test in the database is Geekbench OpenCL, where the R7 M265 records a score of 4929 against the R5 M335's 4745. This gives the R7 M265 a 3.9% advantage, a modest but definitive margin that establishes the pecking order between these two GCN 1.0 parts. The R7 M265 claims the only win in the head-to-head comparison, with a 1-0 record.
Contextualizing the R7 M265's OpenCL score against its nearest rivals shows how tight the competition is at this performance tier. The R7 M265's 4929 sits just 0.1% ahead of the AMD Radeon R7 M360's 4931, a negligible gap that puts the two effectively on par. It also edges out the AMD FirePro W5130M's 4904 by 0.5% and the NVIDIA GeForce GTS 450's 4893 by 0.7%. Interestingly, the R7 M265's score is within 0.6% of the NVIDIA GeForce RTX 5060 Ti 8 GB's 4901, evidence of the unusual clustering of scores around the 4900 mark in this segment.
The R5 M335's position is similarly defined by its immediate rivals. Its average benchmark score of 4752 places it 0.5% behind the AMD Radeon R8 M445DX's 4727, meaning it actually leads that part by half a percent. It trails the AMD Radeon R5 M255's 4788 by 0.7% and the NVIDIA GeForce RTX 3080 12 GB's 4791 by 0.8%. The only part it beats more substantially is the NVIDIA Quadro P400, which scores 4684, a 1.5% gap. The R5 M335's OpenCL score of 4745 is its lower result; its Vulkan score of 4758 is slightly higher, showing a minor API-dependent variance.
The Verdict
From the data alone, the AMD Radeon R7 M265 is the faster GPU. Its 3.9% lead in the head-to-head OpenCL benchmark is unambiguous, and its overall percentile ranking of 29th against all GPUs is one point higher than the R5 M335's 28th percentile. For any user comparing these two purely on compute performance, the R7 M265 is the logical choice. The R7 M265 also benefits from a wider 128-bit memory bus delivering 28.80 GB/s of bandwidth, compared to the R5 M335's 64-bit bus and 14.40 GB/s, which in real-world texture-heavy workloads could widen the gap beyond what the synthetic score suggests.
However, the R5 M335 is not without its own merits. Its pixel rate of 8.240 GPixel/s is 24.8% higher than the R7 M265's 6.600 GPixel/s, and its texture rate of 20.60 GTexel/s also exceeds the R7 M265's 19.80 GTexel/s. The R5 M335 posts a higher FP32 throughput of 659.2 GFLOPS versus the R7 M265's 633.6 GFLOPS. These figures indicate that the R5 M335 is not universally slower; it is a differently balanced chip that may handle fill-rate-bound tasks more capably. The R5 M335 also offers Vulkan support in the benchmark suite, with a score of 4758, while the R7 M265 has no recorded Vulkan result.
The verdict depends on the workload. For general OpenCL compute, the R7 M265 wins. For scenarios where pixel throughput or raw FP32 math matters more, the R5 M335's architectural balance gives it an edge. There is no single "best" across all metrics, but the head-to-head benchmark crown goes to the R7 M265.
Where Each One Wins
The AMD Radeon R7 M265 wins in the direct comparison and in memory bandwidth. Its 128-bit memory interface provides double the bus width of the R5 M335's 64-bit interface, resulting in exactly double the bandwidth: 28.80 GB/s versus 14.40 GB/s. The R7 M265 also has more shading units (384 vs 320), more texture mapping units (24 vs 20), and the same 8 ROPs. It leads in the Geekbench OpenCL test with a 3.9% margin. These attributes make it better suited for tasks that are sensitive to memory throughput and shader count, such as gaming at moderate resolutions or compute workloads that access large datasets.
The AMD Radeon R5 M335 wins in raw throughput metrics despite its smaller configuration. It achieves a higher pixel rate of 8.240 GPixel/s compared to the R7 M265's 6.600 GPixel/s, and a higher texture rate of 20.60 GTexel/s versus 19.80 GTexel/s. Its FP32 performance of 659.2 GFLOPS is also 4% higher than the R7 M265's 633.6 GFLOPS. The R5 M335 achieves this with fewer shading units (320 vs 384) and fewer TMUs (20 vs 24), indicating its clocks are likely higher, although the base and boost clock fields are not populated in the data. This suggests the R5 M335 is tuned for higher-frequency operation, which helps fill-rate-bound scenarios like simple 3D rendering or pixel-heavy post-processing effects.
The R5 M335 also has a dedicated Vulkan benchmark score of 4758, whereas the R7 M265 has no Vulkan result recorded. Both parts support DirectX 12 (11_1), OpenGL 4.6, and Vulkan 1.2.170, so API compatibility is identical, but the R5 M335's Vulkan performance is documented while the R7 M265's is not.
FAQ
Q: Which GPU has the higher Geekbench OpenCL score?
A: The AMD Radeon R7 M265 scores 4929, which is 3.9% higher than the AMD Radeon R5 M335's 4745 in the head-to-head test.
Q: How does the R5 M335 compare to its nearest rival, the R5 M255?
A: The R5 M335's average benchmark score is 4752, which is 0.7% lower than the R5 M255's 4788, so the R5 M255 holds a slight lead.
Q: Is the R7 M265 faster than the R7 M360?
A: The R7 M265 scores 4929 while the R7 M360 scores 4931, a delta of 0%, meaning the two GPUs are effectively identical in performance.
Q: What memory bandwidth does each GPU provide?
A: The R7 M265 has a 128-bit bus with 28.80 GB/s of bandwidth, while the R5 M335 has a 64-bit bus with 14.40 GB/s of bandwidth.
Q: Does the R5 M335 have any performance advantage over the R7 M265?
A: Yes, the R5 M335 has a higher pixel rate (8.240 GPixel/s vs 6.600 GPixel/s), a higher texture rate (20.60 GTexel/s vs 19.80 GTexel/s), and higher FP32 throughput (659.2 GFLOPS vs 633.6 GFLOPS).
Q: What are the percentile rankings of these GPUs?
A: The R7 M265 is in the 29th percentile of all GPUs, while the R5 M335 is in the 28th percentile.
Architecture Differences
Both GPUs are built on the same GCN 1.0 architecture and use a 28 nm process at TSMC, but they differ substantially in their physical configuration. The R7 M265 uses the Opal chip, which contains 950 million transistors on a 77 mm² die. The R5 M335 uses the Exo chip, which packs 690 million transistors onto a 56 mm² die. Despite the different transistor counts, both achieve the same transistor density of 12.3 million transistors per square millimeter.
The R7 M265's larger chip translates into more execution resources: 384 shading units, 24 texture mapping units, and 8 ROPs. The R5 M335 scales down to 320 shading units and 20 TMUs, while keeping the same 8 ROPs. This configuration difference explains the R7 M265's higher scores in shader-heavy OpenCL workloads. However, the R5 M335 compensates with higher clock speeds, as evidenced by its superior pixel and texture rates despite having fewer units.
Memory architecture is another key differentiator. The R7 M265 features a 128-bit memory bus with 2 GB of DDR3 memory running at 900 MHz (1800 Mbps effective), yielding 28.80 GB/s of bandwidth. The R5 M335 halves the bus to 64 bits and also uses 2 GB of DDR3 at the same 900 MHz clock, but its bandwidth drops to exactly half at 14.40 GB/s. Both use DDR3, so the bandwidth difference is purely a function of bus width.
Both parts share the same API support: DirectX 12 (11_1), OpenGL 4.6, and Vulkan 1.2.170. They also use the same PCIe 3.0 x8 bus interface. The R5 M335 is described as portable-device dependent for display outputs and has no power connectors, indicating it is designed for low-power mobile integration. The R7 M265's display outputs and power connectors are not specified in the data. Both are end-of-life products, with the R7 M265 released in January 2014 and the R5 M335 released in October 2015. Both descend from the Solar System generation and are succeeded by Polaris Mobile.