AMD Radeon R7 M265 vs AMD Radeon R7 M360 Comparison

AMD
RADEON

AMD Radeon R7 M265

CORE STATE Opal
VRAM 2 GB
CLOCK SPEED 825 MHz
TDP —
BUS WIDTH 128 bit
ARCHITECTURE GCN 1.0
nm
PROCESS 28 nm
LAUNCH DATE 2014
VS
AMD
RADEON

Radeon R7 M360

CORE STATE Meso
VRAM 2 GB
CLOCK SPEED 1125 MHz
TDP —
BUS WIDTH 64 bit
ARCHITECTURE GCN 3.0
nm
PROCESS 28 nm
LAUNCH DATE 2015

PERFORMANCE BENCHMARKS

geekbench_opencl
4,929
4,638
geekbench_vulkan
N/A
5,223

Analysis: AMD Radeon R7 M265 vs AMD Radeon R7 M360

# AMD Radeon R7 M360 vs AMD Radeon R7 M265

The AMD Radeon R7 M360 and AMD Radeon R7 M265 are two end-of-life mobile GPUs from AMD's Gem System family, separated by roughly one generation but landing at the same performance tier. Both target the 29th percentile of all GPUs, and their average benchmark scores are nearly identical—4931 for the M360 versus 4929 for the M265. The M265 wins the only direct head-to-head benchmark, but the margin is thin enough to call the matchup a statistical tie.

FAQ

Q: Which GPU has the higher average benchmark score?

A: The AMD Radeon R7 M360 edges out the R7 M265 by a razor-thin margin, scoring 4931 on average compared to 4929 for the M265—a difference of just 0.04%.

Q: How do the two compare in the Geekbench OpenCL test?

A: The R7 M265 wins the Geekbench OpenCL head-to-head with a score of 4929 against the M360's 4638, a delta of -5.9% from the M360's perspective.

Q: Do both GPUs support the same DirectX version?

A: No. The R7 M360 supports DirectX 12 (12_0), while the R7 M265 is limited to DirectX 12 (11_1), meaning the newer M360 has a feature-level advantage.

Q: What is the memory bandwidth difference between the two?

A: The R7 M265 has double the memory bandwidth of the M360: 28.80 GB/s versus 14.40 GB/s, despite both using 2 GB of DDR3 memory at 1800 Mbps effective.

Q: Are the shading unit counts identical?

A: Yes, both GPUs feature 384 shading units, 24 texture mapping units, and 8 raster operation units—the core compute configuration is the same.

Q: Which GPU has a higher boost clock?

A: The R7 M360 boosts to 1125 MHz, significantly higher than the R7 M265's 825 MHz boost, and its base clock of 1100 MHz also exceeds the M265's 725 MHz base.

Architecture Differences

The two GPUs represent different generations of AMD's Graphics Core Next architecture. The R7 M360 is built on GCN 3.0 with the Meso chip, while the R7 M265 uses the older GCN 1.0 architecture with the Opal chip. This architectural gap explains several downstream differences. Both are fabricated on the same 28 nm process at TSMC, but the M360 packs 1,550 million transistors on a 125 mm² die, compared to 950 million transistors on a 77 mm² die for the M265. The transistor density is nearly identical—12.4M per mm² for the M360 versus 12.3M per mm² for the M265—so the size difference comes from the M360's larger absolute transistor count.

The GCN 3.0 architecture in the M360 brings a newer feature set. It supports DirectX 12 (12_0), whereas the M265 is limited to DirectX 12 (11_1). Both GPUs support OpenGL 4.6 and Vulkan 1.2.170, so API compatibility outside DirectX is unchanged. The M360 also lists FP16 performance at 864.0 GFLOPS (1:1 ratio with FP32), while the M265 has no FP16 specification listed—a reflection of the older architecture's lack of dedicated half-precision support.

Clock speeds differ substantially. The M360 runs at 1100 MHz base and 1125 MHz boost, while the M265 operates at 725 MHz base and 825 MHz boost. This clock advantage directly feeds into the M360's higher pixel rate (9.000 GPixel/s versus 6.600 GPixel/s) and texture rate (27.00 GTexel/s versus 19.80 GTexel/s). The FP32 compute also favors the M360: 864.0 GFLOPS versus 633.6 GFLOPS. Despite these raw throughput advantages, the M265's wider memory bus compensates in bandwidth-sensitive workloads.

The Verdict

The data presents a classic architectural trade-off. The R7 M360 offers newer GCN 3.0 features, higher clocks, and more raw compute throughput—864.0 GFLOPS FP32 versus 633.6 GFLOPS—but it is hamstrung by a 64-bit memory bus delivering only 14.40 GB/s. The R7 M265, despite older GCN 1.0 silicon and lower clocks, doubles the memory bandwidth to 28.80 GB/s via a 128-bit bus.

For users prioritizing the latest DirectX feature level, the M360 is the clear choice—DirectX 12 (12_0) support matters for newer titles. For workloads sensitive to memory bandwidth, such as texture-heavy scenes or higher resolutions, the M265's doubled bandwidth gives it a practical edge. The head-to-head Geekbench OpenCL result supports this: the M265 wins 4929 to 4638, a 5.9% margin that likely reflects memory bandwidth advantages in this particular workload.

The average benchmark scores tell a different story, with the M360 at 4931 and the M265 at 4929—a negligible 0.04% difference. Both sit at the 29th percentile of all GPUs, placing them in the same performance class. The nearest rivals list confirms this: the AMD FirePro W5130M scores 4904 (0.6% behind the M360, 0.5% behind the M265), the NVIDIA GeForce RTX 5060 Ti 8 GB scores 4901 (0.6% behind both), and the NVIDIA GeForce GTS 450 scores 4893 (0.8% or 0.7% behind). These deltas are all within noise, meaning any of these four GPUs would deliver comparable real-world performance.

Specification Differences

| Specification | AMD Radeon R7 M360 | AMD Radeon R7 M265 |

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

| Architecture | GCN 3.0 | GCN 1.0 |

| Chip | Meso | Opal |

| Generation | Gem System (R7 M300) | Gem System (R7 M200) |

| Transistors | 1,550 million | 950 million |

| Die Size | 125 mm² | 77 mm² |

| Transistor Density | 12.4M / mm² | 12.3M / mm² |

| Base Clock | 1100 MHz | 725 MHz |

| Boost Clock | 1125 MHz | 825 MHz |

| Memory Bus Width | 64 bit | 128 bit |

| Memory Bandwidth | 14.40 GB/s | 28.80 GB/s |

| Pixel Rate | 9.000 GPixel/s | 6.600 GPixel/s |

| Texture Rate | 27.00 GTexel/s | 19.80 GTexel/s |

| FP32 Performance | 864.0 GFLOPS | 633.6 GFLOPS |

| FP16 Performance | 864.0 GFLOPS (1:1) | Not specified |

| DirectX Support | 12 (12_0) | 12 (11_1) |

| Release Date | 2015-05-04 | 2014-01-08 |

Shared specifications include 2 GB DDR3 memory, 384 shading units, 24 TMUs, 8 ROPs, 900 MHz memory clock with 1800 Mbps effective speed, PCIe 3.0 x8 interface, OpenGL 4.6, Vulkan 1.2.170, TSMC 28 nm process, and end-of-life production status.

Head-to-Head Benchmarks

The only direct comparison available is the Geekbench OpenCL test, where the R7 M265 posts a decisive victory. The M265 scores 4929 against the M360's 4638, a 5.9% delta in favor of the older GPU. This result inverts the raw compute specification hierarchy—the M360's 864.0 GFLOPS FP32 is 36% higher than the M265's 633.6 GFLOPS, yet the M265 still wins the benchmark. Memory bandwidth is the most likely explanation: the M265's 28.80 GB/s is exactly double the M360's 14.40 GB/s, and OpenCL workloads often scale with memory throughput.

The M360's wins are all theoretical rather than benchmark-verified. Its pixel rate of 9.000 GPixel/s exceeds the M265's 6.600 GPixel/s by 36%, and its texture rate of 27.00 GTexel/s beats 19.80 GTexel/s by the same margin. The clock advantage is equally stark—1125 MHz boost versus 825 MHz boost—but these advantages do not translate into a benchmark victory in the available data.

Looking at the broader competitive landscape, both GPUs sit in a tight cluster. The M360's average score of 4931 places it just 0.6% ahead of the AMD FirePro W5130M (4904), 0.6% ahead of the NVIDIA GeForce RTX 5060 Ti 8 GB (4901), and 0.8% ahead of the NVIDIA GeForce GTS 450 (4893). The M265's average of 4929 is 0.5% ahead of the FirePro W5130M, 0.6% ahead of the RTX 5060 Ti, and 0.7% ahead of the GTS 450. These margins are all well within typical run-to-run variance, meaning the entire group of five GPUs is effectively interchangeable in performance.

The single benchmark win for the M265, combined with the near-identical average scores, suggests that users should base their choice on features rather than speed. The M360's GCN 3.0 architecture and DirectX 12 (12_0) support make it the more future-proof option for software that leverages newer APIs. The M265's doubled memory bandwidth gives it an edge in memory-bound scenarios, but the lack of FP16 support and older DirectX feature level are drawbacks. In the end, the data shows two GPUs that perform the same on average, with the M265 taking the one direct benchmark and the M360 offering superior architectural features.

DETAILED SPECIFICATIONS

SPECIFICATION
R7 M265
R7 M360
Core Specs
Shading Units
384
384 0.0%
Shaders
384
384 0.0%
TMUs
24
24 0.0%
ROPs
8
8 0.0%
Compute Units
6
6 0.0%
Clocks
Base Clock
725 MHz
1100 MHz
Boost Clock
825 MHz
1125 MHz
Memory Clock
900 MHz 1800 Mbps effective
900 MHz 1800 Mbps effective
Memory
Memory Size
2 GB
2 GB
VRAM (MB)
2,048
2,048 0.0%
Memory Type
DDR3
DDR3
Memory Bus
128 bit
64 bit
Bandwidth
28.80 GB/s
14.40 GB/s
Cache
L1 Cache
16 KB (per CU)
16 KB (per CU)
L2 Cache
256 KB
128 KB
Performance
Pixel Rate
6.600 GPixel/s
9.000 GPixel/s
Texture Rate
19.80 GTexel/s
27.00 GTexel/s
FP32 (TFLOPS)
633.6 GFLOPS
864.0 GFLOPS
FP64 (TFLOPS)
—
54.00 GFLOPS (1:16)
FP16 (TFLOPS)
—
864.0 GFLOPS (1:1)
Architecture
Architecture
GCN 1.0
GCN 3.0
GPU Name
Opal
Meso
Generation
Gem System (R7 M200)
Gem System (R7 M300)
Process Size
28 nm
28 nm
Transistors
950 million
1,550 million
Die Size
77 mm²
125 mm²
Foundry
TSMC
TSMC
Density
12.3M / mm²
12.4M / mm²
API Support
DirectX
12 (11_1)
12 (12_0)
OpenGL
4.6
4.6
Vulkan
1.2.170
1.2.170
OpenCL
2.1 (1.2)
2.1
Shader Model
6.5 (5.1)
6.5
Physical
Bus Interface
PCIe 3.0 x8
PCIe 3.0 x8
Other
Production
End-of-life
End-of-life
Predecessor
Solar System
Solar System
Successor
Polaris Mobile
Polaris Mobile
View Radeon R7 M265 Details View Radeon R7 M360 Details