RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Eruo Fredoline
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
Glossary / Hardware & infrastructure / CUDA
Hardware & infrastructure

CUDA

CUDA (Compute Unified Device Architecture) is NVIDIA's parallel-computing platform and the dominant API for GPU-accelerated AI. Every major AI framework — PyTorch, TensorFlow, JAX, llama.cpp, vLLM, ExLlamaV2 — has CUDA as its primary or best-supported backend.

CUDA's incumbency creates the "NVIDIA tax": even when AMD GPUs have comparable hardware (more VRAM at lower price), the software ecosystem leans NVIDIA. ROCm (AMD's CUDA equivalent) has improved significantly on Linux but still trails on Windows and on training workloads.

Practical implication for buyers: if you want to run AI without troubleshooting, get an NVIDIA card. If you're comfortable on Linux and willing to file occasional GitHub issues, AMD's price-per-VRAM-GB advantage can be real. Apple Silicon sidesteps the question entirely with the Metal/MLX path.

Practical example

A buyer comparing a used RTX 3090 (24GB, roughly $700) against an RX 7900 XTX (24GB, roughly $800) for local LLM inference picks the 3090 despite the worse price-per-VRAM-dollar ratio, because every quantization tool they plan to use — ExLlamaV2, AWQ, bitsandbytes — assumes CUDA as the primary backend, and ROCm support for those tools on Windows is inconsistent enough to cost real debugging time. A Linux-only shop willing to build llama.cpp with ROCm and stick to GGUF (which has solid ROCm support) could make the AMD card work fine, but for someone who wants pip install to just work, the NVIDIA tax is the price of avoiding a week of troubleshooting. Anyone checking hardware fit before buying can run the target model through /will-it-run to see which backend paths are actually validated.

Related terms

ROCm (AMD)Vulkan computeMetal (Apple)

See also

hardware: rtx-5080hardware: rtx-4090

Reviewed by Eruo Fredoline. See our editorial policy.

Buyer guides
  • Best GPU for local AI →
  • CUDA vs ROCm →
When it doesn't work
  • CUDA out of memory →
  • CUDA driver too old →
  • PyTorch CUDA not available →
  • Windows cannot find CUDA →
Compare hardware
  • RTX 4090 vs RTX 5090 →
Hardware
  • RTX 4090 →
  • RTX 5090 →