Can the NVIDIA H100 NVL run GLIDER?

Yes, it runs well

Runs well. At Q4_K_M it needs about 8.4 GB of 94.0 GB usable and makes one decision in about 169 ms.

Best quant: Q4_K_M
Time per decision: 169 ms
Decisions per second: 5.9/s
Input assumed: 1,024 tokens
Returns: Written feedback, then a score

Best app to run it on the NVIDIA H100 NVL

On Linux

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 PatronusAI/glider

LM Studio Point-and-click: search, download and chat in one window.
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.

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open GLIDER in LM Studio

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

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 GLIDER

Recommended for the NVIDIA H100 NVL: Q4_K_M. 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 Q4_K_M file (opens in a new tab)

huggingface.co/PatronusAI/glider-gguf (opens in a new tab)

ollama run hf.co/PatronusAI/glider-gguf:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/PatronusAI/glider (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 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: S 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs well: How well it runs on the NVIDIA H100 NVL: 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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.	28.2 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.	11.5 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	9.0 / 15
Match score	73.8 / 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 H100 NVL

Quant	Memory needed	Available	Time per decision	Runs	Quality	Download
`Q4_K_M`	8.4 GB	94.0 GB	169 ms	Runs well	62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	8.8 GB	94.0 GB	194 ms	Runs well	64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	9.2 GB	94.0 GB	222 ms	Runs well	65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q8_0`	10.2 GB	94.0 GB	284 ms	Runs well	66Good quality (B) · 66 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`	13.7 GB	94.0 GB	559 ms	Slow	66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Times are for one request with a 1,024-token input and about 150 tokens written. Batching servers process many requests at once.

Other hardware that runs it

62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q4_K_M · 308 ms · Runs well
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q4_K_M · 316 ms · Runs well
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA B200 Q4_K_M · 96 ms · Runs great
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI350X Q4_K_M · 118 ms · Runs great
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI325X Q4_K_M · 133 ms · Runs great
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H200 141GB SXM Q4_K_M · 142 ms · Runs well

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.