AMD Says 2 Ryzen AI Halos Can Run a 400B Model... I Tested It
Credibility score: 53/100 — Mixed Credibility. Several questionable claims detected. Watch with healthy skepticism.
BSmeter analyzed "AMD Says 2 Ryzen AI Halos Can Run a 400B Model... I Tested It" and rated it 53/100 for credibility (a BS score of 47/100 — mixed credibility), on 2026-08-23. Its weakest claim — "Either it works perfectly or the network ruins everything" — scored 20/100 and was flagged as false dilemma. 27 claims were checked against the video transcript. Scores are produced by BSmeter's AI analysis of the transcript, not independent human verification.
Claims analyzed
Tiny pocket box runs 200B, two of them run 400B — Missing Context (45/100)
Calls it pocket-sized while the hardware is two full desktop units — missing the actual size and setup.
Either it works perfectly or the network ruins everything — False Dilemma (20/100)
Sets up two extremes — perfect system or total failure — ignoring the middle ground of 'slow but usable.'
You need proper 10GbE — can't just plug in a cable — Missing Context (45/100)
Implies a switch is mandatory while commenters note auto-MDIX makes direct crossover work on 10GBASE-T.
AMD says you must use a switch between two machines — no direct cable. — Missing Context (45/100)
Claims AMD's instructions forbid direct cable — commenters say 10GBASE-T auto-MDIX should work fine.
Micro Center is the exclusive retailer for Ryzen AI Halo machines. — No Frame (75/100)
Straight fact — no spin, just naming the seller.
OS mismatch blocks clustering — needs both on Linux — No Frame (75/100)
Straight technical obstacle — the machines won't cluster until they run the same OS.
iperf3 shows ~9.4 Gbps — essentially saturating the 10 GbE link — No Frame (75/100)
Real measured throughput, not theory — 9.4 Gbps is basically line rate on a 10 GbE connection.
Windows caps at 96 GB, Linux needs manual tweak — Missing Context (45/100)
States the cap difference like it's a done deal — skips that you must recompile the kernel to hit 120 GB.
Windows locks to 64 GB, hidden from BIOS — Confidence Mismatch (45/100)
Speaks with certainty that BIOS won't show the setting — yet the only proof is that he didn't find it on this model.
Linux TTM command failed too — No Frame (75/100)
Straight reporting of what actually happened on his test unit — no embellishment.
Calls 10 GB connection "good" — skips faster options shown. — Missing Context (45/100)
Top comment calls the 40 Gbps USB-C ports right there — 10 GB suddenly looks slow.
Shows 358 B model while title promises 400 B — slides one past the viewer. — Volume Game (45/100)
Video title says 400 B, then quietly tests 358 B; the 42 B gap never gets addressed.
Quant tweaks give better quality at same size — no data shown — Anonymous Authority (45/100)
Names 'Barttowski' and 'they all' — zero specifics on which techniques or what 'juice' actually means.
Low-bit quants 'probably' ruin output — no test shown — Loaded Language (45/100)
Turns 'might degrade' into 'probably mess up' with zero side-by-side evidence.
8.2 t/s on a 358B MoE model — presented as impressive — Missing Context (45/100)
No baseline comparison — is 8.2 t/s good, bad, or average for this size?
Low power draw and VRAM use — framed as a win — Missing Context (45/100)
Efficiency numbers shown without stating what the second machine is also consuming.
7.6-7.9 tokens/sec on 400B model — real measured speed — No Frame (75/100)
Actual numbers from a live test, no hype attached.
Clustering two Halos combines their memory for bigger models — No Frame (75/100)
Straight fact about tensor parallelism via Rickle; matches independent tests.
Calls software stack 'Rickle Rock Communication Collectives' without explaining why it matters — Anonymous Authority (45/100)
Drops a library name like it explains itself — no one knows what it does or why it's necessary.
Calls 397B model 'much bigger' without context on scale — Missing Context (45/100)
Says 397B is 'much bigger' — compared to what? No baseline given.
Admits the process is brittle but shrugs it off as normal — Missing Context (45/100)
Flags the 15-minute reset loop as a known pain but offers zero alternatives or workarounds.
Personal frustration presented as universal setup warning — Just Vibes (50/100)
One bad flag and 15-minute reload — sounds like a personal war story, not a technical fact.
Labels the split 'tensor parallelism TP=2' as if that alone guarantees success — Confidence Mismatch (45/100)
Names the technique like it proves the 400B model runs — zero tokens/sec or quality numbers attached.
States tensor parallelism is active with TP=2 as fact — No Frame (75/100)
Names the exact technique and parameter — clean, no tricks.
Current stack scales to bigger AMD systems; four-node clusters mentioned. — Missing Context (45/100)
Hints at four-node support but gives zero details on how or when. Tease without substance.
Calls two clustering options 'simple' vs 'mini data center' — no numbers given. — Confidence Mismatch (45/100)
Labels one method 'simple' and the other 'mini data center' without benchmarks or setup time.
Two boxes, 220 GB total, 18 tokens/sec max — real numbers, no hype. — No Frame (75/100)
Drops actual measured numbers instead of marketing fluff. Straight data.
See the full analysis with sources and timestamps →