on

Can the NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition run GLiDE 9B?

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

Yes, it runs great

Runs great. At F16 it needs about 21.5 GB of 96.0 GB usable, with an estimated speed of 65.0 tok/s.

Best quant
F16
Generation speed
65.0 tok/s
Prompt processing
9,975 tok/s
First token (1K prompt)
0.3 s
Largest safe context
256K

Best app to run it on the NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition

On Windows

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • On Windows it runs through WSL2.
vllm serve fastino/GLiDE-9B
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Docker Model Runner Handy if you already work in Docker.

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve fastino/GLiDE-9B
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Docker Model Runner Handy if you already work in Docker.

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 GLiDE 9B

Original weights · Hugging Face

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

huggingface.co/fastino/GLiDE-9B (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at F16, whatever it runs on. Match score 67/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 RTX PRO 6000 Blackwell Max-Q Workstation Edition: 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.22.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.5.2 / 15
Match score67.7 / 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 RTX PRO 6000 Blackwell Max-Q Workstation Edition

Quant Memory needed Available Speed Runs Quality Download
Q2_K 8.8 GB 96.0 GB 455 tok/s Runs great 35Basic quality (D) · 35 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 9.6 GB 96.0 GB 358 tok/s Runs great 42Fair quality (C) · 42 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 10.5 GB 96.0 GB 277 tok/s Runs great 47Fair quality (C) · 47 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 11.3 GB 96.0 GB 229 tok/s Runs great 48Fair quality (C) · 48 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 12.2 GB 96.0 GB 192 tok/s Runs great 49Fair quality (C) · 49 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 14.1 GB 96.0 GB 141 tok/s Runs great 50Fair quality (C) · 50 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 21.5 GB 96.0 GB 65.0 tok/s Runs great 50Fair quality (C) · 50 of 100: how capable the model is at F16, whatever it runs on. Match score 67/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

Quick answers

How much memory does GLiDE 9B need on the NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition 96GB?

At F16 it needs about 21.5 GB. The NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition 96GB has 96.0 GB usable.

How fast is GLiDE 9B on the NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition 96GB?

About 65.0 tok/s at F16, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of GLiDE 9B should I use on the NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition 96GB?

F16. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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?