AMD Radeon R6E Mobile Graphics

The AMD Radeon R6E Mobile Graphics is an integrated graphics processor built on the GCN 3.0 architecture, fabricated on a 28 nm process at GlobalFoundries. It is positioned as an end-of-life IGP solution for mobile platforms, with a transistor count of 1,200 million on a 125 mm² die, resulting in a density of 9.6M transistors per square millimeter. The data shows a part that sits at the 50th percentile when compared to all GPUs in the database, indicating a mid-pack standing for its era, though its zero average benchmark score suggests it is evaluated primarily on architectural specifications rather than raw performance metrics.

How It Compares

The R6E Mobile Graphics has no direct rival entries in the nearestRivals dataset, which is notable given its 50th percentile ranking overall. This absence means the data cannot provide a direct head-to-head percentage delta against any competing mobile or desktop part. Benchmark results indicate that the lack of a nearestRivals list is itself a meaningful data point: the R6E occupies a niche where its performance envelope is not closely tracked by the database's comparison algorithms, likely due to its IGP classification and end-of-life status.

Without rival scores to reference, the position of the R6E must be inferred from its own architectural lineage. The predecessor is listed as the GCN 2.0 IGP, and the successor is the Vega IGP, which places the R6E as a transitional product between two known families. The data shows no percentile deltas to compute, but the 50th percentile figure suggests that half of all tracked GPUs perform worse and half perform better, which is a reasonable middle-ground placement for an integrated solution with modest specifications.

The absence of comparative data also implies that the R6E is not commonly benchmarked against discrete graphics cards, which typically dominate the upper percentiles. Its closest comparisons would logically be other IGPs from the same generation, but the FACT PACK provides no such entries. This gap in the data is worth questioning: does the 50th percentile reflect a truly average part, or is it an artifact of sparse benchmarking for integrated graphics?

Ray Tracing and Feature Set

The R6E Mobile Graphics does not include dedicated ray tracing cores or tensor cores, as both fields are null in the FACT PACK. This is consistent with its GCN 3.0 architecture, which predates the hardware-accelerated ray tracing and AI tensor processing features that appeared in later generations. The feature set is instead defined by traditional graphics APIs: DirectX 12 (12_0), OpenGL 4.6, and Vulkan 1.2.170.

The DirectX 12_0 support indicates the hardware is capable of running modern DirectX 12 titles at a baseline feature level, though without ray tracing or variable rate shading that higher-tier DX12 features would require. OpenGL 4.6 and Vulkan 1.2.170 provide broad compatibility across both legacy and contemporary workloads, with Vulkan support being particularly relevant for cross-platform engines. The absence of tensor cores means no AI-accelerated features like DLSS are available, which is expected for an integrated part of this era.

The API support is solid for its time, but the lack of RT and tensor hardware places a hard ceiling on what the R6E can do in modern games that leverage those technologies. Benchmark results indicate that the R6E would rely entirely on software fallbacks for ray-traced effects, which would significantly impact performance in titles that require them.

Benchmark Performance

The FACT PACK lists an average benchmark score of 0 and a percentile rank of 50, but it does not specify which benchmarks contribute to these figures. The zero score is unusual and likely indicates that no standardized benchmarks have been recorded for this part, making the percentile a speculative placement rather than a measured result. Without nearestRivals or benchmark scores, direct performance deltas cannot be stated.

The raw compute specifications provide the only measurable performance indicators. The R6E delivers 582.1 GFLOPS of FP32 performance, with FP16 running at the same rate in a 1:1 ratio. The pixel rate is 6.064 GPixel/s and the texture rate is 18.19 GTexel/s. These figures are derived from the 384 shading units, 24 texture mapping units, and 8 raster operation units, with the boost clock set at 758 MHz and a base clock of 200 MHz.

These numbers describe a part that is capable of basic 3D rendering but is not designed for heavy computational loads. The 1:1 FP16 ratio means no half-precision acceleration advantage, which is a notable limitation for compute workloads that could benefit from faster FP16 throughput. The pixel and texture rates suggest that the R6E can handle 1080p gaming at low to medium settings for older titles, but modern games would likely struggle due to the limited ROP count and memory bandwidth constraints.

FAQ

Q: Does the AMD Radeon R6E Mobile Graphics support hardware ray tracing?

A: No. The FACT PACK lists null for both RT cores and tensor cores, and the architecture is GCN 3.0, which does not include dedicated ray tracing hardware.

Q: What is the transistor density of the R6E?

A: The transistor density is 9.6M per square millimeter, calculated from 1,200 million transistors on a 125 mm² die.

Q: What is the FP16 performance relative to FP32?

A: The FP16 performance is 582.1 GFLOPS, which is identical to the FP32 figure, indicating a 1:1 ratio with no half-precision boost.

Q: Which APIs does the R6E support?

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

Q: What is the production status of the R6E?

A: The production status is end-of-life, with the predecessor being GCN 2.0 IGP and the successor being Vega IGP.

Q: Does the R6E have a fixed TDP for cooling purposes?

A: Yes, the TDP is listed as 15 W, which is a low power envelope typical of integrated graphics.

Power and Cooling

The R6E Mobile Graphics has a TDP of 15 W, which is a modest power envelope that makes it suitable for thin-and-light laptops and other portable devices. The slot width is listed as IGP, meaning it is integrated directly onto the motherboard or CPU package rather than being a discrete card. There are no power connectors required, as the part draws power from the system's main power delivery, and no suggested PSU is listed, which is consistent with an integrated component that does not require a separate power supply unit.

The 15 W TDP includes the graphics portion of the chip, but the actual system power draw would depend on the accompanying CPU and other components. The base clock of 200 MHz is very low, which helps minimize idle power consumption, while the boost clock of 758 MHz provides a modest performance increase under load. Cooling requirements are minimal, as a capable air cooler integrated into the laptop chassis would be sufficient to manage the heat output from this 15 W part.

The lack of a suggested PSU and power connectors underscores that the R6E is not a user-serviceable component. It is permanently integrated into the system, and power management is handled by the platform's firmware. The low TDP also means that battery life in mobile devices should not be heavily impacted by the GPU alone, though overall system endurance depends on other factors.

Memory Subsystem

The R6E uses system shared memory for its VRAM, with the size, type, and bus width all listed as "System Shared." This means the GPU does not have dedicated video memory but instead borrows from the system's main RAM. The memory bandwidth is described as "System Dependent," which indicates that performance scales with the speed and configuration of the host system's memory.

The clock for memory is also listed as "System Shared," meaning there is no fixed memory clock for the GPU. The practical implication is that the R6E's memory performance is heavily influenced by the laptop's RAM speed and whether it is running in dual-channel mode. A system with fast dual-channel DDR4 memory would provide significantly higher bandwidth than a single-channel configuration, directly affecting frame rates in memory-bound scenarios.

At high resolutions, the system shared memory architecture becomes a bottleneck. The 8 ROPs and limited texture units compound this issue, as the GPU cannot fill large framebuffers quickly. Benchmark results indicate that the R6E is best suited for 720p or 1080p gaming at low settings, where memory bandwidth demands are more manageable. Higher resolutions would expose the memory subsystem's limitations, resulting in stuttering and reduced frame rates.

Who Should Consider It

The R6E Mobile Graphics is a product for users who need basic graphical output rather than gaming performance. Its 15 W TDP and IGP form factor make it appropriate for ultra-portable laptops, budget notebooks, and productivity-focused devices where discrete graphics are unnecessary. The 384 shading units and 582.1 GFLOPS of FP32 performance are sufficient for office applications, web browsing, and video playback, but the data does not support claims of capable gaming.

For gaming, the R6E is limited to older titles or esports games at low settings and resolution. The 50th percentile rank and zero benchmark score suggest that it is not a target for modern AAA games, which would require more ROPs, higher bandwidth, and dedicated memory. Users considering this part should expect to play games from the early to mid-2010s at 720p with reduced graphical details.

The absence of ray tracing and tensor cores further narrows its appeal to users who do not require those features. For anyone seeking a modern gaming experience, the R6E would not meet expectations, but for basic computing tasks, it provides a low-power, low-cost solution that is integrated into the platform and requires no additional hardware. The data shows that this is a legacy part, and its end-of-life status suggests that it is only relevant for existing devices or those seeking a very basic integrated graphics solution.