on

Can the NVIDIA A800 40GB Active run Hemmingway 1.5?

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

Yes, it runs great

Runs great. At Q6_K it needs about 25.2 GB of 40.0 GB usable, with an estimated speed of 49.2 tok/s.

Best quant
Q6_K
Generation speed
49.2 tok/s
Prompt processing
522 tok/s
First token (1K prompt)
2.0 s
Largest safe context
228K

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

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 HemmingwayAI/Hemmingway-1.5
  • 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 Hemmingway 1.5 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 Hemmingway 1.5

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

huggingface.co/bartowski/HemmingwayAI_Hemmingway-1.5-GGUF (opens in a new tab)

ollama run hf.co/bartowski/HemmingwayAI_Hemmingway-1.5-GGUF:Q6_K

Original weights · Hugging Face

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

huggingface.co/HemmingwayAI/Hemmingway-1.5 (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 66Good quality (B) · 66 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_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 great
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.29.8 / 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.14.5 / 15
Match score84.4 / 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 13.9 GB 40.0 GB 117 tok/s Runs great 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 16.3 GB 40.0 GB 91.7 tok/s Runs great 56Good quality (B) · 56 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 19.5 GB 40.0 GB 71.0 tok/s Runs great 63Good quality (B) · 63 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 22.2 GB 40.0 GB 58.6 tok/s Runs great 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 25.2 GB 40.0 GB 49.2 tok/s Runs great 66Good quality (B) · 66 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 31.7 GB 40.0 GB 36.1 tok/s Runs great 67Good quality (B) · 67 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 56.9 GB 40.0 GB 2.1 tok/s Very slowheavy RAM offload 67Good quality (B) · 67 of 100: how capable the model is at F16, whatever it runs on. Match score 52/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 Hemmingway 1.5 need on the NVIDIA A800 40GB Active?

At Q6_K it needs about 25.2 GB. The NVIDIA A800 40GB Active has 40.0 GB usable.

How fast is Hemmingway 1.5 on the NVIDIA A800 40GB Active?

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

Which quantization of Hemmingway 1.5 should I use on the NVIDIA A800 40GB Active?

Q6_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?