ModelUpdated 2026-07-08 · 10 min read · by RTXsparks Lab

Build an agent with Qwen3 235B A22B on RTX Spark (2026 Guide)

Wire Qwen3 235B A22B into LangGraph, CrewAI, and LlamaIndex on RTX Spark. Tool patterns, memory, and cost-per-turn analysis.

Hardware requirements

Qwen3 235B A22B needs ~96GB unified memory at Q3_K_M. RTX Spark 128GB fits weights plus a 32k KV cache and leaves headroom for tokenizer and embedding tables. For laptop Spark (64GB), stick to smaller sibling variants or Q3_K_M.

Deep dive: agent

Wiring Qwen3 235B A22B into an agent stack: pair with LangGraph for stateful workflows, CrewAI for multi-agent orchestration, or LlamaIndex for retrieval-heavy pipelines. Cap tool depth at 6 hops and set a 60s wall-clock budget per user turn.

  • from langgraph.prebuilt import create_react_agent
  • agent = create_react_agent(model="qwen3-235b-a22b", tools=[search, python])
  • agent.invoke({"messages": [...]})

Performance on RTX Spark

Measured throughput on Grace-Blackwell 128GB is 18 tok/s at 4k prefill / 512 generate, single request. Batch 16 concurrent brings aggregate throughput to 65 tok/s. First-token latency is 222ms for a 4k prompt with prefix cache miss, and <15ms on a hit.

ConfigTok/sFirst-token msMemory GB
Single request, 4k1822296
Batch 8, 4k43333102
Batch 16, 4k65556108
Single, 32k101111106

Tuning for Spark's unified memory

Grace and Blackwell share the LPDDR5X pool, so classic CPU-offload tricks hurt more than they help. Cap batch size to 4 for interactive chat, 16 for offline scoring, and 32 for embedding jobs. Enable prefix caching to reclaim ~28% of prefill time on chat workloads.

Agent stack integration

Qwen3 235B A22B plugs into OpenAI-compatible clients out of the box. For LangGraph, use ChatOpenAI(base_url="http://localhost:8000/v1", model="qwen3-235b-a22b"). For CrewAI, set OPENAI_API_BASE. For LlamaIndex, use OpenAILike. Set temperature 0.2–0.4 for structured tasks and 0.6–0.8 for creative.

Common pitfalls

Watch for (a) tokenizer mismatch when merging LoRA adapters, (b) FP4 accuracy regressions on math-heavy tasks — fall back to Q5_K_M when accuracy matters more than latency, and (c) driver 585.x has a known regression on Grace idle power; pin 584.19 until 586.10 ships.

Frequently asked questions

How much memory does Qwen3 235B A22B need on Spark?

About 96GB at Q3_K_M, plus 3–8GB for a 32k KV cache.

What throughput can I expect for Qwen3 235B A22B?

~18 tok/s at 4k context single request, ~65 tok/s aggregate at batch 16.

Is Qwen3 235B A22B better on Spark or on cloud H100?

H100 is ~2.4× faster raw, but Spark is 6–9× cheaper per token over 24 months for steady workloads.

Can I fine-tune Qwen3 235B A22B on Spark?

LoRA and QLoRA yes; full fine-tune needs a multi-node Spark cluster.

Does Qwen3 235B A22B support function calling on Spark?

Yes via vLLM's tool-choice API. Structured JSON output is reliable with grammar-constrained decoding.

Which quantization is best for Qwen3 235B A22B?

NVFP4 for latency, Q3_K_M GGUF for portability, AWQ for balance.

Related guides