Why ASUS ProArt GR1X Might Be Better for AI Inference Than AI Training
Because inference only needs the model's weights and some working memory, while training needs the weights plus gradients and optimiser state, several times more memory and far more compute. A 128GB ASUS ProArt GR1X can hold a 70B model at 4-bit for inference, and in principle a 70B QLoRA fine-tune. Full fine-tuning even an 8B model needs about 128GB by a common rule of thumb, more than the GPU can use on this machine. Training a model from scratch is a data-centre job measured in thousands of GPUs. And as of November 2026, no fine-tuning benchmark on RTX Spark under Windows had been published.
What is the difference between inference, fine-tuning and training?
- Inference means running a finished model: you send a prompt, it generates an answer. The model's weights are only read.
- Fine-tuning means adjusting an existing model with your own data. Light methods such as LoRA and QLoRA train small adapter layers and keep the main model frozen. Full fine-tuning updates every weight.
- Training (pre-training) means building a model from nothing on trillions of tokens. This is what AI labs do on large GPU clusters.
Each step up needs more memory per parameter and much more compute. That's why the same machine can be excellent at one and impractical at another.
How much memory does each job need?
| Job | 8B model | 32B model | 70B model | Fits a 128GB GR1X? |
|---|---|---|---|---|
| Inference, 4-bit (Q4_K_M weights) | About 4.9GB | About 19.8GB | About 42.5GB | Yes, all three, plus context |
| Inference, 16-bit (2 bytes per parameter) | About 16GB | About 64GB | About 140GB | 8B and 32B yes; 70B no |
| QLoRA fine-tune (Unsloth minimum) | 6GB | 26GB | 41GB | Yes on memory; untested on this platform |
| 16-bit LoRA fine-tune (Unsloth minimum) | 22GB | 76GB | 164GB | 8B yes; 32B only if about 96GB goes to the GPU; 70B no |
| Full fine-tune (rule of thumb, about 16 bytes per parameter) | About 128GB | About 512GB | About 1,120GB | No |
Source: model file sizes from Unsloth's GGUF repositories on Hugging Face; fine-tuning minimums from Unsloth's requirements page; the 16-bytes-per-parameter figure is the usual estimate for mixed-precision training with the Adam optimiser (weights, gradients, a full-precision copy and two optimiser states) and excludes activations. "Fits" assumes the GPU can use up to about 96GB, the most reported on same-chip RTX Spark laptops; the default share is about 64GB, and ASUS doesn't document the split on the GR1X. Figures are our calculations.
The pattern is clear. Inference on large models fits comfortably. Adapter-style fine-tuning fits on memory for models up to about 70B at 4-bit. Full fine-tuning doesn't fit even for small models, because the optimiser state multiplies the memory per parameter several times over.
Why is inference the natural fit for the GR1X?
Inference for one or a few users is limited mainly by memory capacity and bandwidth, not raw compute. The GR1X's strength is capacity: 128GB in a 1.1-litre box. Its bandwidth of about 300 GB/s (a reviewer calculation; NVIDIA hasn't published the figure) means mid-sized models run at usable speeds. On a same-chip MSI Prestige N16 laptop, Techtesters measured gpt-oss-120b at about 63 tokens per second. Larger dense models are slower; see running a 70B model on the GR1X.
NVIDIA's own positioning matches this. Its RTX Spark page says you can "build, prototype, fine-tune, and run AI models and agents locally" and run models "up to 120B parameters with 1M context". It doesn't claim training.
A 128GB box is large for inference, adequate for light fine-tuning and nowhere near enough for training. Buy it for the first, try it for the second, and rent the third.
Can you fine-tune on the GR1X?
On memory, yes for LoRA and QLoRA on many models. On software, it's early. As of November 2026:
- CUDA on Windows on Arm is a developer preview, and NVIDIA has warned that some PyTorch workflows can trigger GPU timeouts.
- Unsloth's founder has posted that Unsloth runs natively on RTX Spark, but Unsloth's own requirements page mentions DGX Spark, not RTX Spark. Treat it as promising, not proven.
- NVIDIA has announced a NeMo AutoModel fine-tuning recipe for a FLUX image model on RTX Spark.
- StorageReview's RTX Spark laptop review reported no fine-tuning results, and we found no published LoRA benchmark on any RTX Spark Windows machine.
For comparison, NVIDIA's DGX Spark runs fine-tuning on Linux with its full stack. Its published table shows Llama 3.3 70B QLoRA at 759.8 tokens per second, although the same article's text gives a different figure, so treat it with care. If fine-tuning is a regular part of your work, a GB10 system on Linux is the more proven path today. Our GB10 LoRA and QLoRA guide covers it.
What about training a model from scratch?
That's a different scale entirely. Meta trained Llama 3 405B on clusters of 8,192 and 16,384 H100 GPUs, each running at about 380–430 trillion operations per second in BF16. Compute is the issue, not just memory. The GR1X's headline "up to 1 petaflop" is an FP4 figure, a low-precision format for inference. Training typically runs at BF16 or FP8, where any GPU delivers a fraction of its FP4 peak. We explain the gap in why 1 petaflop doesn't tell you how fast your AI will run.
Small experiments, such as training a tiny model to learn the process, will run. Anything meant for production belongs on rented cloud GPUs or a server. At the AWS Capacity Block rate of about US$5.97 per H100-hour listed on 5 Nov 2026, a short fine-tuning job costs far less than buying hardware for it. Cloud prices change, so check current rates.
So who should buy the GR1X for AI work?
- Good fit: developers and creators who mainly run models, build agents or test prompts, and want large models on a quiet Windows desktop.
- Possible fit: occasional LoRA or QLoRA on small and mid-sized models, once you've confirmed your tools run on Windows on Arm or WSL2.
- Poor fit: regular fine-tuning of large models, full fine-tuning, or training. These need more GPU memory, more compute and mature Linux tooling. See why the GR1X might be the wrong choice for serious AI developers and our memory buying guide.
Buying in Singapore
The ASUS ProArt GR1X is listed at SourceIT as price on request. A SourceIT estimate based on comparable RTX Spark devices (not an official ASUS price) is about S$9,000–10,800 for 128GB/2TB, including GST. For fine-tuning on Linux, the ASUS Ascent GX10 128GB/1TB is S$10,350 and the NVIDIA DGX Spark 4TB is S$9,300. For larger fine-tuning jobs, the RTX PRO 6000 Blackwell Max-Q with 96GB is S$29,100 (all listed 8 Nov 2026). Prices change, so ask for a current quotation. Use Request for Quotation on the product page, call (65) 6978 3502, email Sales@sourceit.com.sg or use our contact page.
Frequently asked questions
Can the ASUS ProArt GR1X train AI models? It can run small training experiments, but it isn't built for training at any meaningful scale. Its strengths are running models (inference) and, potentially, light fine-tuning.
Can I fine-tune a 70B model on the GR1X? On memory, a 70B QLoRA fine-tune needs about 41GB by Unsloth's minimum, which fits a 128GB machine. No fine-tuning benchmark on RTX Spark under Windows had been published as of November 2026, and the CUDA stack is still a developer preview.
Why does full fine-tuning need so much memory? Because training stores gradients and optimiser state alongside the weights. A common estimate is about 16 bytes per parameter, so an 8B model needs about 128GB before activations.
Is the 1 petaflop figure useful for training? Not directly. It's an FP4 figure, a low-precision format used for inference. Training usually runs at BF16 or FP8, where available compute is much lower.
What should I use for fine-tuning instead? For regular fine-tuning, a GB10 system on Linux such as the DGX Spark or ASUS Ascent GX10, a workstation with an RTX PRO 6000, or rented cloud GPUs for occasional large jobs.
SourceIT Approved
Researched and verified by the SourceIT team for Singapore buyers.




