on

Can the NVIDIA A800 40GB Active run Apertus v1.5 70B?

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

Yes, it runs well (tight fit)

Runs well (tight fit). At Q2_K it needs about 34.1 GB of 40.0 GB usable, with an estimated speed of 43.5 tok/s.

Best quant
Q2_K
Generation speed
43.5 tok/s
Prompt processing
195 tok/s
First token (1K prompt)
5.3 s
Largest safe context
25K

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

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/swiss-ai/Apertus-v1.5-70B

On Windows

Docker Model Runner

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

  • Handy if you already work in Docker.
docker model run hf.co/swiss-ai/Apertus-v1.5-70B

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 Apertus v1.5 70B

Original weights · Hugging Face

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

huggingface.co/swiss-ai/Apertus-v1.5-70B (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

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

How it’s rated

Quality 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, 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.20.8 / 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.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 score74.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 A800 40GB Active

Quant Memory needed Available Speed Runs Quality Download
Q2_K 34.1 GB 40.0 GB 43.5 tok/s Runs welltight fit 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 40.6 GB 40.0 GB 25.2 tok/s Runs welloffloads to RAM 55Good quality (B) · 55 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 49.2 GB 40.0 GB 4.7 tok/s Slowoffloads to RAM 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 56.4 GB 40.0 GB 2.7 tok/s Very slowheavy RAM offload 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 64.3 GB 40.0 GB — Won't run 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 81.6 GB 40.0 GB — Won't run 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 149 GB 40.0 GB — Won't run 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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 Apertus v1.5 70B need on the NVIDIA A800 40GB Active?

At Q2_K it needs about 34.1 GB. The NVIDIA A800 40GB Active has 40.0 GB usable.

How fast is Apertus v1.5 70B on the NVIDIA A800 40GB Active?

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

Which quantization of Apertus v1.5 70B should I use on the NVIDIA A800 40GB Active?

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