on

Can the NVIDIA A800 40GB Active run Hermes 4 70B?

62Good quality (B) · 62 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q3_K_M it needs about 39.9 GB of 40.0 GB usable, with an estimated speed of 35.0 tok/s.

Best quant
Q3_K_M
Generation speed
35.0 tok/s
Prompt processing
199 tok/s
First token (1K prompt)
5.1 s
Largest safe context
8K

Best app to run it on the NVIDIA A800 40GB Active

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open Hermes 4 70B 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 Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open Hermes 4 70B 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? Hermes 4 70B 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 Hermes 4 70B

Recommended for the NVIDIA A800 40GB Active: Q3_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 Q3_K_M file (opens in a new tab)

huggingface.co/unsloth/Hermes-4-70B-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Hermes-4-70B-GGUF:Q3_K_M

Original weights · Hugging Face

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

huggingface.co/NousResearch/Hermes-4-70B (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 62Good quality (B) · 62 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q3_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: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welltight fit
How well it runs on the NVIDIA A800 40GB Active: 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.28.0 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.14.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 score81.0 / 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 A800 40GB Active

Quant Memory needed Available Speed Runs Quality Download
Q2_K 33.5 GB 40.0 GB 44.4 tok/s Runs great 51Fair quality (C) · 51 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 39.9 GB 40.0 GB 35.0 tok/s Runs welltight fit 62Good quality (B) · 62 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 48.3 GB 40.0 GB 5.1 tok/s Slowoffloads to RAM 70Great quality (A) · 70 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 55.4 GB 40.0 GB 2.8 tok/s Very slowheavy RAM offload 71Great quality (A) · 71 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 63.1 GB 40.0 GB — Won't run 73Great quality (A) · 73 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 80.1 GB 40.0 GB — Won't run 74Great quality (A) · 74 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
F16 146 GB 40.0 GB — Won't run 74Great quality (A) · 74 of 100: how capable the model is at F16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (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

Quick answers

How much memory does Hermes 4 70B need on the NVIDIA A800 40GB Active?

At Q3_K_M it needs about 39.9 GB. The NVIDIA A800 40GB Active has 40.0 GB usable.

How fast is Hermes 4 70B on the NVIDIA A800 40GB Active?

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

Which quantization of Hermes 4 70B should I use on the NVIDIA A800 40GB Active?

Q3_K_M. 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?