on

Can the NVIDIA GeForce RTX 5090 run NorthCUA Nano?

52Fair quality (C) · 52 of 100: how capable the model is at F16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 21.3 GB of 32.0 GB usable, with an estimated speed of 54.8 tok/s.

Best quant
F16
Generation speed
54.8 tok/s
Prompt processing
8,019 tok/s
First token (1K prompt)
0.3 s
Largest safe context
256K

Best app to run it on the NVIDIA GeForce RTX 5090

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open NorthCUA Nano in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open NorthCUA Nano in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

Want an agent? NorthCUA Nano supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download NorthCUA Nano

Recommended for the NVIDIA GeForce RTX 5090: F16. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the F16 file (opens in a new tab)

huggingface.co/mradermacher/NorthCUA-Nano-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/NorthCUA-Nano-GGUF:F16

Original weights · Hugging Face

Full-precision files from beipo-ai, for fine-tuning, vLLM, Transformers.

huggingface.co/beipo-ai/NorthCUA-Nano (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 52Fair quality (C) · 52 of 100: how capable the model is at F16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great
How well it runs on the NVIDIA GeForce RTX 5090: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.23.4 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score78.4 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA GeForce RTX 5090

Quant Memory needed Available Speed Runs Quality Download
Q2_K 6.2 GB 32.0 GB 384 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 7.1 GB 32.0 GB 302 tok/s Runs great 43Fair quality (C) · 43 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 8.2 GB 32.0 GB 234 tok/s Runs great 49Fair quality (C) · 49 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 9.1 GB 32.0 GB 193 tok/s Runs great 50Fair quality (C) · 50 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 10.2 GB 32.0 GB 162 tok/s Runs great 51Fair quality (C) · 51 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 12.4 GB 32.0 GB 119 tok/s Runs great 52Fair quality (C) · 52 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 21.3 GB 32.0 GB 54.8 tok/s Runs great 52Fair quality (C) · 52 of 100: how capable the model is at F16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?