Platforms · AMD

X100 / Strix Halo

AMD's flagship targeting AI and robotics edge workloads. Strix Halo represents an x86-based alternative to the Jetson ecosystem, offering strong CPU performance with unified memory for LLM/VLM workloads.

16x Zen 5 (32T) @ 5.1 GHz RDNA 3.5 Up to 128 GB LPDDR5X 45-120 W

Max Power at 120 W

CPU available
81.9%
26.2 of 32 cores free
Missions completed
10
in 900 s
Control loop misses
0.46/s
against a 30 Hz target
VLM queries completed
34 of 47
scene-understanding queries

CPU

Total load, its distribution across cores, and the clock behind it.

#CPU utilization

Total CPU utilization across all cores, sampled once a second for the length of the run.

Data table (4 rows)
MetricMeanp50p95Max
CPU total (%)18.1318.0021.4023.30
Peak core (%)89.3599.00100.00100.00
Mean core (%)18.1318.0021.4023.40
Active cores (%)73.5775.0090.60100.00

Source: max_power/amd_strix_halo · CSV

Supporting charts

Per-core utilization over time

#Per-core utilization over time

One row per core. Persistent dark bands are cores that stay pinned for the whole run.

Data table (32 rows)
CoreMean (%)
014.7
121.5
228.4
334.4
435.2
529.9
640.5
718.6
86.9
919.4
105.4
114.5
126.5
1316.1
149.2
1511.7
1610.0
1714.3
1818.0
1955.9
2023.3
2163.1
2230.8
2311.8
245.5
2510.3
265.0
274.4
285.1
297.1
306.3
316.7

Source: max_power/amd_strix_halo · CSV

Per-core utilization distribution

#Per-core utilization distribution

Every per-core sample in the run, bucketed into 5% bands.

Data table (20 rows)
Utilization band (%)Samples
0–55700
5–108734
10–153390
15–202732
20–251858
25–301179
30–35902
35–40684
40–45561
45–50510
50–55778
55–60300
60–65247
65–70146
70–75138
75–8097
80–8578
85–9071
90–9573
95–100622

Source: max_power/amd_strix_halo · CSV

CPU clock frequency

#CPU clock frequency

Sustained CPU clock frequency under load.

Data table (1 rows)
MetricMeanp50p95Max
CPU frequency (MHz)2,644.942,754.053,512.764,230.60

Source: max_power/amd_strix_halo · CSV

GPU and memory

Accelerator load from the VLM workload, and the memory it leaves behind.

#GPU utilization

GPU utilization while the VLM issues queries continuously.

Data table (3 rows)
MetricMeanp50p95Max
GPU utilization (%)95.1399.00100.00100.00
GPU clock (MHz)2,756.602,874.002,900.002,900.00
Effective throughput (GHz)265.66284.23289.90290.00

Source: max_power/amd_strix_halo · CSV

Supporting charts

System memory usage

#System memory usage

System memory in use across the run, as a share of the total fitted.

Data table (3 rows)
MetricMeanp50p95Max
RAM (%)47.3047.9048.6049.40
RAM used (MB)58,632.8859,358.5560,230.1261,304.30
Swap (%)0.000.000.000.00

Source: max_power/amd_strix_halo · CSV

GPU memory usage

#GPU memory usage

GPU memory in use, as reported by the platform driver.

Data table (2 rows)
MetricMeanp50p95Max
GPU memory used (MB)638.58640.20645.40645.40
GPU memory total (MB)2,048.002,048.002,048.002,048.00

Source: max_power/amd_strix_halo · CSV

Power and thermal

Board draw and the thermal margin left underneath it.

#Board power

Board power draw across the run, against the configured TDP.

Data table (1 rows)
MetricMeanp50p95Max
Board power (W)118.24120.00124.03139.00

Source: max_power/amd_strix_halo · CSV

Supporting charts

CPU and GPU temperature

#CPU and GPU temperature

CPU and GPU package temperature under sustained load, against a 100 °C throttle point.

Data table (2 rows)
MetricMeanp50p95Max
CPU temperature (°C)77.0076.5087.1296.38
GPU temperature (°C)72.4474.0079.0083.00

Source: max_power/amd_strix_halo · CSV

Clock against temperature

#Clock against temperature

A clock that falls as temperature climbs is thermal throttling; a flat clock means the platform held its performance for the whole run.

Data table (2 rows)
MetricMeanp50p95Max
CPU temperature (°C)77.0076.5087.1296.38
CPU clock (MHz)2,644.942,754.053,512.764,230.60

Source: max_power/amd_strix_halo · CSV

Compute delivered per watt

#Compute delivered per watt

CPU utilization divided by instantaneous board power, showing how efficiency moves as the workload shifts between planning and perception.

Data table (3 rows)
MetricValue
Mean available compute per watt (GHz-cores/W)0.586
Mean GPU utilization per watt (%/W)0.805
Mean board power (W)118.2

Source: max_power/amd_strix_halo · CSV

System behaviour

Stability, I/O, and process load, the context around the headline counters.

#CPU against GPU utilization

Each point is one second of the run. A tight cluster means the two resources move together; a wide spread means one is waiting on the other.

Data table (2 rows)
MetricMeanp50p95Max
CPU total (%)18.1318.0021.4023.30
GPU utilization (%)95.1399.00100.00100.00

Source: max_power/amd_strix_halo · CSV

Supporting charts

Rolling stability

#Rolling stability

Standard deviation over a 30-sample window. Spikes are moments the load became bursty rather than steady.

Data table (2 rows)
SeriesWindow (samples)
CPU total30
GPU utilization30

Source: max_power/amd_strix_halo · CSV

Network throughput

#Network throughput

Sensor data arriving over the wired DDS link from the simulation machine. Every platform is offered the same load.

Data table (3 rows)
MetricMeanp50p95Max
Network received (MB/s)66.9467.0067.4068.50
Network sent (MB/s)0.280.300.400.40
Network errors1.001.001.001.00

Source: max_power/amd_strix_halo · CSV

Disk throughput

#Disk throughput

Disk read and write throughput across the run.

Data table (2 rows)
MetricMeanp50p95Max
Disk read (MB/s)0.000.000.000.00
Disk write (MB/s)0.050.000.104.70

Source: max_power/amd_strix_halo · CSV

Load average

#Load average

Run-queue depth. A load average well above the core count means threads are waiting for a core rather than running on one.

Data table (3 rows)
MetricMeanp50p95Max
Load average (1m)5.025.156.547.23
Load average (5m)3.744.415.185.31
Load average (15m)2.022.193.343.45

Source: max_power/amd_strix_halo · CSV

Process count

#Process count

Total processes on the machine while the benchmark runs.

Data table (1 rows)
MetricMeanp50p95Max
Process count566.85564.00582.00583.00

Source: max_power/amd_strix_halo · CSV

All metrics for Max Power

Mean / p95 / max for every captured metric, across every run in this category.
MetricAMD Strix Halo
Meanp95Max
CPU Total (%)18.1321.4023.30
CPU Frequency (MHz)2,644.943,512.764,230.60
Peak Core Utilization (%)89.35100.00100.00
Mean Core Utilization (%)18.1321.4023.40
Active Cores (%)73.5790.60100.00
RAM Usage (%)47.3048.6049.40
RAM Used (MB)58,632.8860,230.1261,304.30
RAM Total (MB)126,428.70126,428.70126,428.70
Swap Usage (%)0.000.000.00
GPU Utilization (%)95.13100.00100.00
GPU Clock (MHz)2,756.602,900.002,900.00
GPU Memory Clock (MHz)1,000.001,000.001,000.00
GPU Effective Throughput (GHz)265.66289.90290.00
GPU Memory Used (MB)638.58645.40645.40
GPU Memory Total (MB)2,048.002,048.002,048.00
VCN Utilization (%)0.000.000.00
Board Power (W)118.24124.03139.00
CPU Temperature (°C)77.0087.1296.38
GPU Temperature (°C)72.4479.0083.00
Disk Read (MB/s)0.000.000.00
Disk Write (MB/s)0.050.104.70
Disk Usage (%)9.409.409.40
Net Recv (MB/s)66.9467.4068.50
Net Sent (MB/s)0.280.400.40
Network Errors1.001.001.00
Load Average (1m)5.026.547.23
Load Average (5m)3.745.185.31
Load Average (15m)2.023.343.45
Process Count566.85582.00583.00

Raw samples: CSV · max_power/amd_strix_halo

Max Power (AI Workload Optimized) at 120 W

CPU available
85.6%
27.4 of 32 cores free
Missions completed
10
in 900 s
Control loop misses
0.49/s
against a 30 Hz target
VLM queries completed
76 of 80
scene-understanding queries

CPU

Total load, its distribution across cores, and the clock behind it.

#CPU utilization

Total CPU utilization across all cores, sampled once a second for the length of the run.

Data table (4 rows)
MetricMeanp50p95Max
CPU total (%)14.3913.8018.7021.30
Peak core (%)77.6976.80100.00100.00
Mean core (%)14.3813.8018.7021.50
Active cores (%)61.8059.4090.60100.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Supporting charts

Per-core utilization over time

#Per-core utilization over time

One row per core. Persistent dark bands are cores that stay pinned for the whole run.

Data table (32 rows)
CoreMean (%)
012.7
114.8
222.2
333.7
431.9
528.1
632.1
714.8
84.6
913.7
103.6
112.9
124.6
139.8
145.8
157.4
167.8
1712.7
1815.0
1945.0
2018.0
2150.3
2226.8
239.3
243.6
256.3
263.2
272.9
283.4
294.7
304.1
314.7

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Per-core utilization distribution

#Per-core utilization distribution

Every per-core sample in the run, bucketed into 5% bands.

Data table (20 rows)
Utilization band (%)Samples
0–59893
5–106903
10–153154
15–202375
20–251511
25–30969
30–35703
35–40610
40–45488
45–50450
50–55747
55–60214
60–65135
65–7087
70–7577
75–8058
80–8561
85–9030
90–9531
95–100304

Source: max_power_optimized/amd_strix_halo_optimized · CSV

CPU clock frequency

#CPU clock frequency

Sustained CPU clock frequency under load.

Data table (1 rows)
MetricMeanp50p95Max
CPU frequency (MHz)3,192.943,410.854,193.194,714.80

Source: max_power_optimized/amd_strix_halo_optimized · CSV

GPU and memory

Accelerator load from the VLM workload, and the memory it leaves behind.

#GPU utilization

GPU utilization while the VLM issues queries continuously.

Data table (3 rows)
MetricMeanp50p95Max
GPU utilization (%)94.55100.00100.00100.00
GPU clock (MHz)2,707.542,855.502,889.002,894.00
Effective throughput (GHz)265.53285.40288.90289.40

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Supporting charts

System memory usage

#System memory usage

System memory in use across the run, as a share of the total fitted.

Data table (3 rows)
MetricMeanp50p95Max
RAM (%)66.7166.7066.8066.90
RAM used (MB)81,724.5581,715.2081,825.3381,975.40
Swap (%)0.000.000.000.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

GPU memory usage

#GPU memory usage

GPU memory in use, as reported by the platform driver.

Data table (2 rows)
MetricMeanp50p95Max
GPU memory used (MB)300.94300.40302.40302.40
GPU memory total (MB)2,048.002,048.002,048.002,048.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Power and thermal

Board draw and the thermal margin left underneath it.

#Board power

Board power draw across the run, against the configured TDP.

Data table (1 rows)
MetricMeanp50p95Max
Board power (W)116.14119.10126.06134.04

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Supporting charts

CPU and GPU temperature

#CPU and GPU temperature

CPU and GPU package temperature under sustained load, against a 100 °C throttle point.

Data table (2 rows)
MetricMeanp50p95Max
CPU temperature (°C)83.2783.2589.7593.75
GPU temperature (°C)71.5672.0081.0084.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Clock against temperature

#Clock against temperature

A clock that falls as temperature climbs is thermal throttling; a flat clock means the platform held its performance for the whole run.

Data table (2 rows)
MetricMeanp50p95Max
CPU temperature (°C)83.2783.2589.7593.75
CPU clock (MHz)3,192.943,410.854,193.194,714.80

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Compute delivered per watt

#Compute delivered per watt

CPU utilization divided by instantaneous board power, showing how efficiency moves as the workload shifts between planning and perception.

Data table (3 rows)
MetricValue
Mean available compute per watt (GHz-cores/W)0.753
Mean GPU utilization per watt (%/W)0.814
Mean board power (W)116.1

Source: max_power_optimized/amd_strix_halo_optimized · CSV

System behaviour

Stability, I/O, and process load, the context around the headline counters.

#CPU against GPU utilization

Each point is one second of the run. A tight cluster means the two resources move together; a wide spread means one is waiting on the other.

Data table (2 rows)
MetricMeanp50p95Max
CPU total (%)14.3913.8018.7021.30
GPU utilization (%)94.55100.00100.00100.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Supporting charts

Rolling stability

#Rolling stability

Standard deviation over a 30-sample window. Spikes are moments the load became bursty rather than steady.

Data table (2 rows)
SeriesWindow (samples)
CPU total30
GPU utilization30

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Network throughput

#Network throughput

Sensor data arriving over the wired DDS link from the simulation machine. Every platform is offered the same load.

Data table (3 rows)
MetricMeanp50p95Max
Network received (MB/s)66.8967.0067.2068.10
Network sent (MB/s)5.717.807.908.00
Network errors0.000.000.000.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Disk throughput

#Disk throughput

Disk read and write throughput across the run.

Data table (2 rows)
MetricMeanp50p95Max
Disk read (MB/s)0.000.000.002.70
Disk write (MB/s)0.050.000.105.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Load average

#Load average

Run-queue depth. A load average well above the core count means threads are waiting for a core rather than running on one.

Data table (3 rows)
MetricMeanp50p95Max
Load average (1m)4.654.836.497.17
Load average (5m)3.474.214.875.06
Load average (15m)1.852.033.113.14

Source: max_power_optimized/amd_strix_halo_optimized · CSV

Process count

#Process count

Total processes on the machine while the benchmark runs.

Data table (1 rows)
MetricMeanp50p95Max
Process count512.83506.00534.00535.00

Source: max_power_optimized/amd_strix_halo_optimized · CSV

All metrics for Max Power (AI Workload Optimized)

Mean / p95 / max for every captured metric, across every run in this category.
MetricAMD Strix Halo (optimized)
Meanp95Max
CPU Total (%)14.3918.7021.30
CPU Frequency (MHz)3,192.944,193.194,714.80
Peak Core Utilization (%)77.69100.00100.00
Mean Core Utilization (%)14.3818.7021.50
Active Cores (%)61.8090.60100.00
RAM Usage (%)66.7166.8066.90
RAM Used (MB)81,724.5581,825.3381,975.40
RAM Total (MB)126,424.40126,424.40126,424.40
Swap Usage (%)0.000.000.00
GPU Utilization (%)94.55100.00100.00
GPU Clock (MHz)2,707.542,889.002,894.00
GPU Memory Clock (MHz)1,000.001,000.001,000.00
GPU Effective Throughput (GHz)265.53288.90289.40
GPU Memory Used (MB)300.94302.40302.40
GPU Memory Total (MB)2,048.002,048.002,048.00
VCN Utilization (%)0.000.000.00
Board Power (W)116.14126.06134.04
CPU Temperature (°C)83.2789.7593.75
GPU Temperature (°C)71.5681.0084.00
Disk Read (MB/s)0.000.002.70
Disk Write (MB/s)0.050.105.00
Disk Usage (%)32.8032.8032.80
Net Recv (MB/s)66.8967.2068.10
Net Sent (MB/s)5.717.908.00
Network Errors0.000.000.00
Load Average (1m)4.656.497.17
Load Average (5m)3.474.875.06
Load Average (15m)1.853.113.14
Process Count512.83534.00535.00

Raw samples: CSV · max_power_optimized/amd_strix_halo_optimized

Verdict

Production-capable for this workload and the platform with the most CPU left over with 82% of the CPU bandwidth available to application developers. It can absorb work that today is split between a Jetson Orin and a separate x86 computer.

Strong

  • Highest available CPU capability per watt. Can absorb at least an additional eight cores of load with no change in application performance.
  • Completed every mission while holding the lowest control-loop miss rate.
  • Best in class GPU performance inline with NVIDIA Jetson Thor.
  • Unified memory: free system RAM is directly available to the GPU for larger models.
  • x86, so existing x86-only robotics software runs without porting.

Weakness

  • In the balanced-power category it shows more control-loop misses than at max power, because the generic BIOS balanced profile allocates TDP toward the saturated GPU rather than the CPU.
  • No equivalent of the Jetson software ecosystem (yet).
  • Thermal design in a sealed enclosure may need closer evaluation.

Specification

The vendor's numbers on the left; what this platform's sensor drivers actually cost it, measured on real hardware, on the right.

Vendor specification
CPU16x Zen 5 (32T) @ 5.1 GHz
GPU architectureRDNA 3.5
GPU cores2560 Shaders (40 CUs)
Memory bandwidth256 GB/s
NPU / DLAXDNA 2 (50 TOPS)
RAMUp to 128 GB LPDDR5X
Power (TDP)45-120 W
Product pageAMD
Measured sensor-driver load (fraction of one core, per instance)
3D LiDAR0.160
2D safety LiDAR0.014
RGBD camera0.520
Total for the robot's sensor suite2.07 cores

Setup instructions for this platform are in the platform setup guide.

Results by TDP or Configuration

Each category fixes a TDP power budget or optimized configuration and runs the workload on every platform. Open one to see how this platform behaved under those conditions, and how it compared against the others.