AMD Radeon R7 M260DX

The AMD Radeon R7 M260DX is an integrated graphics processor (IGP) that pairs a GCN 1.0 architecture core with a system-shared memory design. Built on the Jet chip at TSMC's 28 nm process, it was introduced on 2014-01-06 as part of the Gem System Hybrid (Rx M200) generation. The GPU is now end-of-life, but its specification sheet still offers a clear picture of its intended role: a low-power integrated solution for portable devices. In the benchmark database, it holds a 50th percentile position among all GPUs, meaning it sits exactly at the median of the tracked population.

Benchmark Performance

The raw compute numbers for the R7 M260DX are modest but internally consistent. The GPU contains 320 shading units, 20 texture mapping units, and 8 ROPs. The base clock is 955 MHz, and the boost clock reaches 1030 MHz. From these figures, the FP32 compute is 659.2 GFLOPS, the texture rate is 20.60 GTexel/s, and the pixel rate is 8.240 GPixel/s. The boost clock is only 75 MHz higher than the base clock, a narrow margin that suggests the GPU is thermally constrained and cannot sustain large clock excursions. The 28 nm process node from TSMC houses 690 million transistors on a die size of 56 mm², yielding a transistor density of 12.3 million transistors per square millimeter. That density figure is a product of the 28 nm era; modern GPUs on smaller nodes achieve far higher densities, but this chip's modest transistor count is appropriate for an integrated part.

The 50th percentile ranking is the single most informative comparison metric available. Half of the GPUs in the database score below the R7 M260DX, and half score above it. For an integrated GPU, this median position is notable — many IGPs cluster at the bottom of the distribution because they lack dedicated memory and have limited shading resources. The R7 M260DX, with 320 shading units and a 1030 MHz boost, manages to land at the midpoint. However, the average benchmark score is listed as 0, and the benchmarks array is empty. This means no standardized performance measurement has been recorded for this specific part in the database. The percentile ranking is therefore derived from the spec-sheet parameters rather than from an actual executed benchmark. This distinction matters when interpreting the data: the R7 M260DX is positioned at the median by specification, but its real-world performance could deviate depending on the host system's memory configuration and cooling.

The pixel rate of 8.240 GPixel/s, driven by 8 ROPs, is the most limiting metric. ROP throughput governs fill-rate-bound operations such as high-resolution rendering and multi-sampling antialiasing. The texture rate of 20.60 GTexel/s, from 20 TMUs, is comparatively stronger relative to the pixel rate — a texture-to-pixel ratio of roughly 2.5:1. This suggests the GPU is better suited to texture-rich scenes at moderate resolutions than to high-pixel-count workloads. The FP32 figure of 659.2 GFLOPS places the GPU in the entry-level compute tier, capable of light general-purpose GPU workloads but not competitive with mid-range discrete parts.

Ray Tracing and Feature Set

The R7 M260DX predates the era of hardware ray tracing. The RT cores field is null, and the tensor cores field is also null. There is no dedicated silicon for ray-traced geometry intersection or for AI-based tensor operations. Any ray tracing in games would have to be performed on the 320 shader units using compute shaders, which is impractical for real-time performance at any reasonable resolution. Similarly, the absence of tensor cores means no hardware acceleration for features like DLSS or other AI upscaling techniques. The GPU's feature set is defined entirely by the GCN 1.0 architecture, which was AMD's first unified shader architecture.

On the API front, the R7 M260DX supports DirectX 12 (11_1), OpenGL 4.6, and Vulkan 1.2.170. The DirectX 12 entry is qualified with the 11_1 feature level. This is an important distinction: the driver exposes the DirectX 12 API, but the hardware feature level is capped at 11_1. That means some DirectX 12 features that require higher feature levels — such as certain bindless resources or advanced rasterizer ordered views — may not be available. OpenGL 4.6 is a mature version of the API, and Vulkan 1.2.170 is a relatively recent Vulkan revision, which gives the GPU broad compatibility with modern cross-platform engines. The combination of OpenGL 4.6 and Vulkan 1.2.170 means the R7 M260DX can run a wide range of current software, provided the performance is adequate for the workload. The display outputs are listed as "Portable Device Dependent," which reflects the IGP's role in laptops and other portable systems where the display path is controlled by the host device.

How It Compares

The nearestRivals field in the data is empty, so there are no direct rival names, scores, or percentage deltas to report. This is itself a meaningful data point: the R7 M260DX is an integrated GPU, and the database may not track direct competitors for IGP parts with the same rigor as discrete GPUs. Without rival scores, the comparison must rely on the percentile position and the architectural facts. The 50th percentile is the only comparative metric available. It tells us the GPU is not a bottom-tier part — it outperforms half of the database population. But it also tells us it is not a high performer — the upper half of the population is out of reach.

The IGP classification is central to understanding this GPU's position. The slot width is "IGP" and the bus interface is "IGP," meaning the chip is integrated into the host processor or chipset rather than installed in a discrete slot. This has two implications. First, the GPU cannot be upgraded or replaced independently of the host system. Second, the GPU shares the system's memory bandwidth, which ties its performance to the host platform's RAM speed and channel configuration. A discrete GPU with dedicated VRAM would not have this dependency, but it would also consume more power and require a larger physical footprint. The R7 M260DX's 28 nm process and 690 million transistors are the defining physical characteristics; a modern integrated GPU on a newer node would likely offer better performance per watt, but the data does not include such a comparison.

FAQ

Q: What architecture does the AMD Radeon R7 M260DX use?

A: It uses the GCN 1.0 architecture, built on the Jet chip at TSMC's 28 nm process node.

Q: Does the R7 M260DX support hardware ray tracing?

A: No. The RT cores field is null, meaning there is no dedicated ray tracing hardware.

Q: What is the FP32 compute performance of this GPU?

A: The FP32 performance is 659.2 GFLOPS, based on 320 shading units at a 955 MHz base clock and 1030 MHz boost clock.

Q: How much dedicated video memory does the R7 M260DX have?

A: None. The memory size, type, and bus width are all listed as "System Shared," meaning it uses the host system's RAM.

Q: What API versions does the R7 M260DX support?

A: It supports DirectX 12 (11_1), OpenGL 4.6, and Vulkan 1.2.170.

Q: Is the R7 M260DX still in production?

A: No. Its production status is end-of-life, and it was released on 2014-01-06.

Memory Subsystem

The memory subsystem of the R7 M260DX is defined by what it lacks. There is no dedicated VRAM; the memory size is "System Shared," the memory type is "System Shared," and the bus width is "System Shared." The bandwidth is listed as "System Dependent." This is the most consequential aspect of the GPU's design. A discrete GPU typically has its own GDDR or HBM memory with a wide dedicated bus, allowing high and predictable bandwidth. The R7 M260DX has none of that. It reads and writes through the same memory controller as the CPU, competing with the host processor for bandwidth. The actual bandwidth available to the GPU is therefore a function of the system's RAM type, speed, and channel configuration — two systems with the same R7 M260DX could deliver meaningfully different GPU performance if their memory subsystems differ.

For high-resolution workloads, this shared-memory design is a significant handicap. At resolutions above 1080p, the frame buffer grows, and the GPU needs to access more texture data and geometry. With system-shared memory, every access must traverse the host memory bus, which is shared with the CPU and other system components. The pixel rate of 8.240 GPixel/s and texture rate of 20.60 GTexel/s are the GPU-side throughput limits, but the memory subsystem is likely to become the bottleneck before those limits are reached in many scenarios. The 690 million transistors and 56 mm² die size are fixed properties of the chip, but the memory performance is not — it is a variable that depends on the host platform. This makes the R7 M260DX difficult to characterize in isolation. The GPU's compute resources are fixed, but its memory behavior is not. The system-dependent bandwidth is the key caveat in any performance assessment of this part.