Intel HD Graphics 530 Mobile

Intel HD Graphics 530 Mobile is an integrated GPU from Intel’s Generation 9.0 architecture, built around the Skylake GT2 chip on Intel’s 14 nm+ process with a die size of 123 mm². It was released on 2015-08-31 and its production status is End-of-life. The database entry records a 50th percentile position among all GPUs and an average benchmark score of 0; the benchmarks array is empty, and no nearest rivals are listed.

Benchmark Performance

The benchmark record for this part is empty. No entries appear in the benchmarks array, so there are no measured frame rates, synthetic scores, or workload-specific results to analyze. The nearestRivals array is also empty, which means no exact percentage deltas can be computed against any named competitor. The only aggregate comparative values are the percentileVsAllGpus field, set to 50, and the average benchmark score, set to 0. In isolation, the 50th percentile would place the GPU at the midpoint of the database’s all-GPU distribution, but the empty benchmark table provides no supporting test scores for that placement.

Specification-level figures are the only concrete performance data available. The GPU uses 192 shading units, 24 texture mapping units, and 3 raster output units. Its base clock is 350 MHz, and its boost clock is 950 MHz; no game clock is specified. From those resources, the recorded pixel rate is 2.850 GPixel/s, the texture rate is 22.80 GTexel/s, and FP32 throughput is 364.8 GFLOPS. FP16 throughput is listed as 729.6 GFLOPS at a 2:1 ratio. The FP16 figure is exactly twice the FP32 figure, and it is not accompanied by tensor cores, since the tensor core field is null.

These rates define a modest integrated part. The TDP is 15 W, and the slot width is IGP, so the design is bounded by a small power envelope and integrated placement rather than by an external power connector. Because the benchmarks array is empty, there is no evidence in the data of how this part behaves in sustained workloads. The boost clock of 950 MHz is substantially higher than the 350 MHz base clock, but the database does not include a sustained clock figure or a game clock figure. Without benchmark entries, the actual duration of boost operation cannot be determined from the available fields.

The practical consequence of the empty benchmark data is that all comparisons must be structural. The 192 shading units, 24 TMUs, and 3 ROPs are the hardware blocks that any workload will use. The pixel and texture rates are fixed output ceilings. The FP32 and FP16 throughput values are the compute ceilings. None of these numbers is a measured game score, but they are the only numerical performance evidence in the database for this GPU.

Memory Subsystem

The memory configuration is entirely System Shared. Memory size is System Shared, memory type is System Shared, and bus width is System Shared. There is no dedicated VRAM pool listed for this GPU. Bandwidth is described as System Dependent, so no fixed bandwidth value exists in the specification. This means the GPU’s memory capacity and memory throughput are functions of the host platform, not of the GPU itself.

For high-resolution workloads, the lack of dedicated VRAM is important because the GPU must rely on shared system memory for frame buffers and textures. The database records no bus width and no bandwidth number for this part, so it is not possible to quote a memory bandwidth ceiling. The effective bandwidth will change depending on the system memory configuration, which is precisely what the “System Dependent” field indicates.

The fixed limits in the memory subsystem are therefore the core-side throughput values. Pixel rate is 2.850 GPixel/s, and texture rate is 22.80 GTexel/s. Those rates do not scale with memory type, because they are derived from the GPU’s own rendering blocks. However, the overall experience at high resolutions will also depend on how much system memory is available and how the platform allocates it to the integrated GPU. The database does not provide a separate shared-memory bandwidth figure, so no high-resolution bandwidth conclusion can be made beyond the fact that bandwidth is system-dependent.

Ray Tracing and Feature Set

The rtCores field is null, and the tensorCores field is null. The data therefore records no dedicated ray tracing hardware and no dedicated tensor acceleration hardware. This is a notable part of the feature set, since some GPUs in the database report those blocks explicitly. Here, neither block is present.

The API list is more modern than the absence of RT/tensor cores might suggest. The supported DirectX version is 12 with feature level 12_1. OpenGL support is 4.6, and Vulkan support is 1.3. These are the only API fields in the fact pack. Feature level 12_1 and Vulkan 1.3 expose contemporary API entry points, but they do not themselves indicate hardware ray tracing support. The API fields are separate from the null RT core data, so the correct reading is that the GPU supports these API versions while lacking dedicated ray tracing hardware.

Display outputs are recorded as Portable Device Dependent. That means the physical output configuration is determined by the portable device rather than by a fixed set of ports on the GPU itself. The bus interface is Ring Bus, which is consistent with an integrated part whose data path is on the processor’s ring interconnect. The slot width is IGP. No power connector data is recorded, and no suggested PSU figure is recorded, which is expected for a 15 W integrated GPU rather than a discrete card.

FAQ

Q: What architecture and process node does the Intel HD Graphics 530 Mobile use?

A: It belongs to Intel’s Generation 9.0 architecture. Its chip is Skylake GT2, built on Intel’s 14 nm+ process. The die size is 123 mm², and the foundry is Intel.

Q: Does this GPU have dedicated VRAM?

A: No. Memory size, memory type, and bus width are all recorded as System Shared. Bandwidth is System Dependent, so there is no dedicated VRAM figure in the data.

Q: Does it support hardware ray tracing or tensor operations?

A: The rtCores field is null and the tensorCores field is null, so no dedicated ray tracing or tensor hardware is recorded. It supports DirectX 12 (12_1), OpenGL 4.6, and Vulkan 1.3, but those API versions are not paired with RT core or tensor core data.

Q: What are the clock speeds?

A: The base clock is 350 MHz and the boost clock is 950 MHz. No game clock is listed in the database.

Q: What are the fill rates and compute throughput?

A: Pixel rate is 2.850 GPixel/s, texture rate is 22.80 GTexel/s, FP32 throughput is 364.8 GFLOPS, and FP16 throughput is 729.6 GFLOPS at a 2:1 ratio.

Q: Is the Intel HD Graphics 530 Mobile still in production?

A: No. Its production status is End-of-life. It was released on 2015-08-31.

How It Compares

The nearestRivals array for the Intel HD Graphics 530 Mobile is empty. There are no rival names, rival scores, or deltaPct values in the database entry, so the part cannot be positioned against any specific product. The only comparative data point is the overall percentileVsAllGpus of 50, which places it at the middle of the all-GPU distribution, alongside an average benchmark score of 0 and an empty benchmarks array. Without rival entries, there is no percentage lead or deficit to report against any named GPU. The comparison section is therefore limited to the structural specifications: 192 shading units, 24 TMUs, 3 ROPs, 350 MHz base clock, 950 MHz boost clock, 15 W TDP, and system-shared memory with bandwidth dependent on the host system.