Radeon R9|R7|R5

AMD Radeon R9 380X

AMD Radeon R9 380X
Representative GIGABYTE product image. Board design, dimensions and power limits can vary by model.Source coverage for this specification group is incomplete.

At a glance

Launch date
Architecture
Graphics Core Next
Compute units
32
Memory
4 GB GDDR5

Hardware specifications

Compute

Compute units
32
Stream processors
2,048

Clocks

Boost clock
970 MHz

Memory

Capacity
4 GB
Memory type
GDDR5
Bus width
256-bit
Bandwidth
182 GB/s

Measured evidence

Market and rendering evidence

Historical launch pricing for AMD Radeon R9 380X preserves source terms such as USD, MSRP and SEP. It is shown separately from one workload-specific community benchmark.

Blender Cycles rendering

Not enough compatible Blender 4.5 data

Backend
HIP
Confidence
Missing
Submission count
0 submissions
Cohort
Blender 4.5.0 on Windows using HIP across the standard Blender Benchmark scenes

This is a Cycles rendering community median in estimated samples per minute. It is not gaming FPS or an overall GPU rating.

Open Blender Open Data source

Retrieved

Open Blender Open Data methodology

Evidence record

Sources and verification

Specifications for AMD Radeon R9 380X were checked against the linked source material. Last verified .

AMD Radeon R9 380X uses the official ASUS November 19 2015 announcement date because AMD's later introduction summary has no exact day. It must not be described as verified same-day retail availability. AMD's current support page prints 64-bit but AMD's own 2016 results release and GIGABYTE both publish 256-bit, so the canonical interface is 256-bit. The support page's 182 GB/s value is retained without increasing its precision. Graphics Core Next is supported at the AMD R9 300 family level and has medium confidence for this exact model. The image context comes from the reviewed owner-supplied local GIGABYTE image at resources/Graphics Card Photos/GIGABYTE GC/61. R9 380X.png and is not asserted by the web specification sources. represented_model stays absent because the manifest verifies box-level GPU identity rather than an exact board SKU.