By Evan Vega
A DGX Spark cluster was build for an SEO agency. Here’s why that is the wrong answer.
A widely shared post announced four NVIDIA DGX Spark systems in a home server room, running local LLMs around the clock for SEO and AI-search research: vendor-claim tracking, pricing watch, SERP labelling, a “citability” model, contradiction detection, and analysis of HAR files captured from AI search products. Novel Cognition read it closely. The research agenda is credible. The case for the hardware is not made: the post offers page counts, keyword counts and a roughly $100 monthly power estimate, but no throughput, accuracy or utilization figures.
A post announced four NVIDIA DGX Spark systems running local LLMs 24/7 for SEO and AI-search research, including HAR-file analysis of AI search products. The HAR idea is good; the hardware case isn’t
NVIDIA lists each DGX Spark with 128 GB of unified memory and 273 GB/s of bandwidth, so four provide 512 GB across four separate systems rather than one machine. An M3 Ultra Mac Studio holds up to 256 GB in a single pool. Exo Labs measured the Spark prefilling prompts 3.8 times faster than the M3 Ultra and the Mac generating tokens 3.4 times faster; the right choice depends on the bottleneck, which the post never measured. Apple now leases Macs through Apple Upgrade on 24- or 36-month terms (a personal lease; businesses use Apple’s business financing), which lets an agency measure its real workload before committing roughly $18,800 to four Sparks at the reported price.
The full comparison is at Four Sparks vs One Mac Studio and Lease the Mac, Measure First.
A HAR (HTTP Archive) file logs a browser’s network traffic: requests, responses, timing and, depending on the capture, streamed events. When an AI search product streams its queries or candidate sources to the browser, a HAR can capture them, which makes it genuinely useful evidence. But the post claims HARs show “every search turn,” “every page it fetched,” and every page “fetched and then declined to cite.” Each of those requires the product to label that event in browser-visible traffic. Whatever the provider does on its own servers and never sends the browser, a HAR cannot see.
The research pays when it answers a decision a client will act on, measured by accepted findings rather than traces processed, with repeated runs, controls and deterministic parsing before any model is involved. See What a HAR File Actually Sees and Does HAR Analysis Pay?.
Sixty thousand pages a month averages about 2,000 a day; fetching, snapshotting, diffing and extracting them is data engineering. A weekly program of 14,930 keywords is mostly a SERP-collection problem. An LLM is useful for the ambiguous remainder after code has done its work, and the post never says how large that remainder is. Its citability model is trained on pages marked “cited but not retrieved,” a label that depends on retrieval most outside observers cannot see. What decides quality is the harness: snapshots, a typed evidence store, a changed-material queue, a cheap-first model router, schema-checked output and evaluation sets. Details at Six Jobs, Not One and Model Choice and the Harness.
How much more billable, accurate, timely research does the fourth Spark produce over the first Mac Studio, and what does that earn? Until someone can answer, four Sparks are defensible as research or as marketing, not as an operating necessity. The moat is the experiment, the evidence and the analyst.
The full file is at sparkoverbuild.novcog.us.com. Primary sources: NVIDIA’s DGX Spark hardware overview, Exo Labs’ Spark and Mac Studio test, Apple’s Apple Upgrade announcement, and the W3C HAR specification.
Part of the Frontier Watch Series: Read the previous investigation
More Coverage:
→ Read this investigation on North Denver Tribune
→ Coverage from Daily Colorado News
