NVIDIA Announces DGX Spark 64GB: A 1-PetaFLOP Grace Blackwell Desktop for Local AI Agents, Fine-Tuning, and Inference
NVIDIA announced a 64GB DGX Spark desktop with up to 1 petaFLOP FP4 for local agents and fine-tuning.
NVIDIA announced a 64GB DGX Spark desktop, offered through Acer, ASUS, Dell, Gigabyte, HP, and MSI, built on the GB10 Grace Blackwell superchip. It provides up to 1 petaFLOP of sparse FP4 compute, 64GB of coherent LPDDR5x at 273 GB/s, ConnectX-7 200GbE networking, and DGX OS with PyTorch, Jupyter, and Ollama. NVIDIA says it fits today’s 30–35B-class open models, while two systems can cluster for 128GB of memory; the existing 128GB Spark remains available. Availability is listed for October 23, 2026.
- GB10 pairs a Blackwell GPU with a 20-core Grace Arm CPU.
- 64GB unified LPDDR5x is shared by CPU and GPU over NVLink-C2C.
- NVIDIA targets roughly 30–35B open models, including quantized Muse Glimmer.
- Two 64GB units can cluster for 128GB and up to 2 PFLOPS.
- Sales begin October 23, 2026, through NVIDIA and OEM partners.
Full article1,422 words · extracted from marktechpost.com · click to collapse
NVIDIA announced a new 64GB configuration of DGX Spark — from Acer, ASUS, Dell, Gigabyte, HP and MSI — its GB10-powered desktop AI system. It gives developers a way to start with one system for local models and agents, then cluster two 64GB units for 128GB of memory across the cluster and more compute when workloads grow.
The direct message is: Run open models and always-on agents on your own desk, then cluster DGX Spark system as the work grows – instead of on a metered API.
The timing is not accidental. Agents burn tokens continuously through tool calls, retries, long context, and multi-step plans. Token consumption has grown 14x since early 2026. On a cloud API, every one of those tokens is billed. On owned hardware, there is no per-token fee.
The 64GB model keeps the same GB10 Grace Blackwell superchip, NVIDIA CUDA accelerated AI software stack, and ConnectX-7 networking as the original — updated with 64GB of unified LPDDR5x instead of 128GB. NVIDIA positions that as enough for today’s most capable 30–35B class open models. NVIDIA continues to offer the 128GB DGX Spark for larger single-box workloads, and clustering 64GB units adds memory and compute together.
What is Inside the Box
GB10 pairs a Blackwell GPU with 5th-generation Tensor Cores and a 20-core Grace Arm CPU. The GPU delivers up to 1 petaFLOP of FP4 AI compute, with sparsity.
| Spec | DGX Spark 64GB |
| Superchip | NVIDIA GB10 Grace Blackwell |
| CPU | 20-core Arm (10× Cortex-X925 + 10× Cortex-A725) |
| AI compute | Up to 1 petaFLOP FP4 (with sparsity) |
| Memory | 64GB LPDDR5x, coherent unified |
| Memory bandwidth | 273 GB/s |
| Storage | 1, 2, or 4TB NVMe M.2, self-encrypting |
| Networking | ConnectX-7 NIC, 200GbE; Wi-Fi 7, BT 5.3 |
| Display | 1× HDMI 2.1a |
| OS | NVIDIA DGX OS (Ubuntu-based) |
| Size / weight | 150 × 150 × 50.5 mm / 1.2 kg |
| Max local model size | Up to 100B parameters |
| Availability | Oct 23, 2026 — NVIDIA Marketplace, OEM partners, retail |
Source: NVIDIA specifications.
Unified memory is the key design choice: The CPU and GPU share one pool over NVLink-C2C, at 5x the bandwidth of PCIe Gen 5. There is no copying weights between system RAM and VRAM. For agents, that means several models, their KV caches, and tool processes live in one address space.
The software is ready on first boot: DGX OS ships with the NVIDIA AI stack, including PyTorch, Jupyter, and Ollama. NVIDIA NemoClaw installs with a single command. It adds privacy and security controls to OpenClaw agents. NVIDIA OpenShellTM, part of the NVIDIA Agent ToolkitTM, adds policy-based guardrails on top. NVIDIA NemotronTM models are optimized for the box.
It runs on a standard wall outlet: No server room, no special cooling. That is important for an agent meant to run around the clock.
Built-in networking for clustering: ConnectX-7 lets two DGX Spark 64GB systems cluster for 128GB of memory and more compute. NVIDIA Sync Cluster Assistant simplifies setup.
Which Open Models Fit in 64GB
Hardware is half the story. The other half is that 30B-class open models got good enough for agent work.
| Model | Developer | Type | Footprint | Role on a Spark |
| Muse Glimmer | Meta | 29.6B dense, text + image, Apache 2.0 | ~17GB (quantized) | Main agent model |
| Nemotron 3.5 Lightning | NVIDIA | 30B MoE (30B-A3B) | NVFP4 checkpoint | Fast executor for long-running agents |
| Qwen3.8-27B | Alibaba Qwen | 27B dense | ~13.5GB weights (4-bit) | General agent and coding |
Footprints are weight-only estimates; KV cache and runtime overhead come on top.
Muse Glimmer is the main model. Meta distilled it from Muse Spark, the model family behind the Meta AI assistant. It targets local agents: reliable tool calls, long multi-step tasks, and recovery from failures. Meta reports 51.2 on SWE-Bench Pro and 75.5 on MCP Atlas. Context runs to 131K tokens. It is also available as an NVIDIA NIM.
Full BF16 Glimmer needs 55GB+, which leaves almost nothing for context. The ~17GB quantized build is the practical choice on 64GB.
Larger models like DeepSeek V4 Flash need more than one box. NVIDIA’s own benchmarks run it on 4 64 GB clustered Sparks.
5 Things You Can Build on One Box
1. An always-on personal agent
Install Hermes and point it at Muse Glimmer or Nemotron 3.5 Lightning. Give it tools: your GitHub repos, a test runner, an RSS feed of arXiv categories. Let it run overnight.
By morning it has triaged new issues, reproduced a failing test, and drafted a pull request for review. It has also summarized the 30 papers you would never have opened. Your private notes, code, and email never leave the machine.
2. Fine-tune a coding model on your own repo
QLoRA on a 70B model fits in 64GB. Train it on your codebase, internal docs, and past PR reviews. Then serve it locally as a coding assistant that knows your conventions.
NVIDIA measured ~18,400 tokens/s on a single node for nanochat distributed fine-tuning.
3. A day-1 model evaluation bench
A new open-weight model drops on Hugging Face. Pull it through Ollama or vLLM the same day. Run your own question set against it.
Score accuracy, then measure time to first token (TTFT) and tokens per second. Compare it against your current model. There is no API bill for re-running the eval 50 times.
4. A multi-model agent team
Unified memory lets several models share one pool. Run Bonsai 2 as a router, and Glimmer as the main reasoning agent. That is roughly 23GB of weights.
The rest covers KV cache, the OS, and tool processes. When a problem exceeds local capacity, the agent can send a sanitized question to a larger cloud model.
5. Edge and robotics prototyping
Fine-tune a vision transformer for a specific task, like spotting anomalies on a factory floor camera. Validate it locally with the same CUDA stack. Then deploy it to an NVIDIA Jetson device at the edge.
When One Box is Not Enough: Clustering with NVIDIA Sync
Every DGX Spark ships with ConnectX-7 at 200GbE. Clustering is a native feature, not an add-on.
| Setup | Pooled memory | AI compute (FP4) | Connection |
| 1 Spark (64GB) | 64GB | Up to 1 PFLOP | — |
| 2 Sparks (64GB each) | 128GB | Up to 2 PFLOPS | Direct QSFP cable, no switch |
| 2 Sparks (128GB each) | 256GB | Up to 2 PFLOPS | Direct QSFP cable, no switch |
| 3 Sparks (128GB each) | 384GB | Up to 3 PFLOPS | QSFP ring, no switch |
| 4 Sparks (128GB each) | 512GB | Up to 4 PFLOPS | 200GbE switch (QSFP56-DD, RoCE v2) |
Source: NVIDIA. 3-node compute derived from per-unit specs.
NVIDIA states 2 clustered 64GB units deliver up to 1.7x the performance of one 128GB DGX Spark. The reason is doubled AI compute and bandwidth: 2 units provide up to 546 GB/s combined, double a single box.
NVIDIA Sync is the management layer. The Windows and macOS app discovers Sparks on your network and manages SSH access. Its Cluster Assistant configures ConnectX-7 networking for up to 4 systems. Nodes can also connect across locations over a Tailscale mesh, with no cloud in the data path.
The pattern is quite clear. Clustering roughly halves time to first token per doubling and scales fine-tuning near-linearly. Decode improves more modestly, about 1.4x at 4 nodes. For agents that read long inputs, the TTFT gain is the one that matters.
Step-by-step multi-node guides, including vLLM on stacked Sparks, are at build.nvidia.com/spark.
What It is, and What It is Not
- Not a chat server for 100 users: 273 GB/s of bandwidth limits concurrent decode throughput.
- Built for long-input, short-output work: Reading a repo, a log dump, or a paper stack, then writing a short result.
- 64GB caps one box at 100B parameters: For more, cluster 2 units or choose the 128GB configuration.
Key Takeaways
- DGX Spark 64GB keeps GB10, 1 PFLOP FP4, and the full NVIDIA AI stack.
- 64GB runs today’s 30–35B class open models, like Qwen 3.8 27B and Nemotron 3.5 Lightning.
- Best uses: always-on agents, QLoRA fine-tuning, and day-1 model evals — no per-token fees.
- 2 units cluster over ConnectX-7 via NVIDIA Sync for 128GB and up to 1.7x a 128GB Spark.
- Available October 23; the DGX Spark 128GB remains available.
Check out the DGX Spark product page, NVIDIA Sync, and DGX Spark playbooks.
Thanks to the NVIDIA team for the thought leadership / resources for this article. This article is sponsored by NVIDIA.
Jean-marc Mommessin
Jean-marc is a successful AI business executive .He leads and accelerates growth for AI powered solutions and started a computer vision company in 2006. He is a recognized speaker at AI conferences and has an MBA from Stanford.