Can the NVIDIA GeForce RTX 5090 run TMax 4B?

Yes, it runs great

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

Best quant: F16
Generation speed: 123 tok/s
Prompt processing: 17,923 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

Command line + local API · runs on llama.cpp, vLLM

Handy if you already work in Docker.

docker model run hf.co/allenai/tmax-4b

Text Generation WebUI
vLLM For one person, llama.cpp-based apps are about as fast and use smaller GGUF files.

On Linux

Docker Model Runner

Command line + local API · runs on llama.cpp, vLLM

Handy if you already work in Docker.

docker model run hf.co/allenai/tmax-4b

vLLM For one person, llama.cpp-based apps are about as fast and use smaller GGUF files.
SGLang For one person, llama.cpp-based apps are about as fast and use smaller GGUF files.

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 TMax 4B

Original weights · Hugging Face

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

huggingface.co/allenai/tmax-4b (opens in a new tab)

No sign-in needed.

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 75/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.	27.5 / 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.	7.9 / 15
Match score	75.3 / 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`	4.2 GB	32.0 GB	858 tok/s	Runs great	42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q3_K_M`	4.5 GB	32.0 GB	675 tok/s	Runs great	51Fair quality (C) · 51 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q4_K_M`	5.0 GB	32.0 GB	523 tok/s	Runs great	57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q5_K_M`	5.5 GB	32.0 GB	432 tok/s	Runs great	59Good quality (B) · 59 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q6_K`	5.9 GB	32.0 GB	363 tok/s	Runs great	60Good quality (B) · 60 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q8_0`	6.9 GB	32.0 GB	266 tok/s	Runs great	61Good quality (B) · 61 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.	All files (opens in a new tab)
`F16`	10.9 GB	32.0 GB	123 tok/s	Runs great	61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.	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

61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Q8_0 · 40.4 tok/s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER F16 · 46.0 tok/s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER F16 · 50.3 tok/s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti F16 · 61.3 tok/s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 F16 · 65.7 tok/s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 Q8_0 · 51.7 tok/s · Runs great

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.