SaulLM-large TPS calculator
Each card below is assessed against this model at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from the card's memory bandwidth and the size of the model once compressed.
Calculated for this model
Smallest card that fits
A100 SXM4 80 GB
80 GB · Q3_K_M · 16.5 tok/s
Fastest card
H100 NVL 94 GB
29.1 tok/s · 94 GB
Which GPUs can run SaulLM-large?
Set the inputs, read the answer
A longer conversation needs more memory, which can push this model off smaller cards.
Hides cards that would only fit the model by compressing it below this point.
37 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
29.1
tok/s
17–47 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 77.8 GB | IQ4_XS | Tight |
|
27.4
tok/s
16–44 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 102.4 GB | Q5_K_M | Tight |
|
27.2
tok/s
16–44 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 69.6 GB | Q3_K_M | Tight |
|
27.2
tok/s
16–44 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 69.6 GB | Q3_K_M | Tight |
|
24.8
tok/s
15–40 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 77.8 GB | IQ4_XS | Tight |
|
24.0
tok/s
14–38 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 151.7 GB | Q8_0 | Tight |
|
24.0
tok/s
14–38 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 151.7 GB | Q8_0 | Comfortable |
|
23.3
tok/s
14–37 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 86.0 GB | Q4_K_M | Tight |
|
23.3
tok/s
14–37 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 86.0 GB | Q4_K_M | Tight |
|
22.3
tok/s
13–36 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 102.4 GB | Q5_K_M | Tight |
|
21.3
tok/s
13–34 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 118.8 GB | Q6_K | Tight |
|
21.3
tok/s
13–34 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 118.8 GB | Q6_K | Tight |
|
19.2
tok/s
12–31 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 151.7 GB | Q8_0 | Comfortable |
|
19.2
tok/s
12–31 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 151.7 GB | Q8_0 | Comfortable |
|
16.5
tok/s
10–26 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 69.6 GB | Q3_K_M | Tight |
|
16.5
tok/s
10–26 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 69.6 GB | Q3_K_M | Tight |
|
16.5
tok/s
10–26 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 69.6 GB | Q3_K_M | Tight |
|
16.5
tok/s
10–26 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 69.6 GB | Q3_K_M | Tight |
|
16.5
tok/s
10–26 · low confidence |
H100 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Oct 2022 | 69.6 GB | Q3_K_M | Tight |
|
16.5
tok/s
10–26 · low confidence |
H800 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 69.6 GB | Q3_K_M | Tight |
|
15.7
tok/s
9–25 · low confidence |
A100 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Jun 2021 | 69.6 GB | Q3_K_M | Tight |
|
15.7
tok/s
9–25 · low confidence |
A800 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Nov 2022 | 69.6 GB | Q3_K_M | Tight |
|
14.1
tok/s
8–22 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 151.7 GB | Q8_0 | Comfortable |
|
13.7
tok/s
8–22 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 102.4 GB | Q5_K_M | Tight |
|
13.7
tok/s
8–22 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 102.4 GB | Q5_K_M | Tight |
Speeds are estimates for a single request — one conversation at a time — calculated from memory bandwidth, model size and quantisation. Real throughput varies with the inference runtime and its version. Figures published by hardware vendors measure many simultaneous requests and are much higher.
On record
Full specification
Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.
Origin
Who built this model, where, and when it was published.
- Organisation
- Equall.ai
- Organisation type
- Industry
- Country
- United States of America
- Published
- 28 July 2024
- Authors
- Pierre Colombo, Telmo Pires, Malik Boudiaf, Rui Melo, Dominic Culver, Sofia Morgado, Etienne Malaboeuf, Gabriel Hautreux, Johanne Charpentier, Michael Desa
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Question answering
- Base model
- Mixtral 8x22B
Size
How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.
- Parameters
- 141B
- Training data
- tokens
- Batch size
- 4
SaulLM-large is based on Mixtral-141B-Instruct, a Transformer model with a Mixture of Experts that selects only 2 out of 8 experts to process tokens for each layer [1]. https://arxiv.org/abs/2407.19584
This is a text generation model so dataset size is measured in number of words. Assuming the pre-training dataset contains 540B tokens and English words only, Dataset size ~= 540e9 tokens * 0.75 words / token = 405e9 words = 4.05e11 words 1. https://arxiv.org/abs/2407.19584 2. https://docs.google.com/document/d/1XWLyMzcVfDv4eFQX3yPgM8MZ3_Q1phtIFz9GKv4_KaM/edit?tab=t.0#heading=h.ieihc08p8dn0
Training compute
The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.
- Fine-tuning compute
- 1.3 × 10²³ FLOP
The paper doesn’t provide a clear description of the fine-tuning dataset, so there’s insufficient information to calculate the fine-tuning compute.
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Training hardware
- AMD Radeon Instinct MI250
- Chips used
- 384
- Hardware utilisation
- HFU 40.0%
- Power draw
- 378.7 kW
Compute Infrastructure "The computational backbone for the continuous pretraining phase of our project consists of 384 AMD MI250 GPUs. We can reach 40% GPU utilization with our implementation. For instruction fine-tuning and preference optimization, we rely on 64 AMD MI250 GPUs. Evaluation protocols are executed on a single node of AMD MI250 GPU." The utilization measurement description, "We can reach 40% GPU utilization", sounds like they're reporting HFU.
Availability
Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.
- Weights
- Open — downloadable
- Model access
- Open weights (unrestricted)
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Likely
- Citations
- 44
Sources
Where this record came from and when it was last checked.
- Reference
- SaulLM-54B & SaulLM-141B: Scaling Up Domain Adaptation for the Legal Domain
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs for SaulLM-large
Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.
- 01 H100 NVL 94 GB 94 GB · 3,940 GB/s · IQ4_XS 29.1 tok/s
- 02 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q5_K_M 27.4 tok/s
- 03 H800 SXM5 80 GB · 3,360 GB/s · Q3_K_M 27.2 tok/s
- 04 H100 SXM5 80 GB 80 GB · 3,360 GB/s · Q3_K_M 27.2 tok/s
- 05 H100 SXM5 94 GB 94 GB · 3,360 GB/s · IQ4_XS 24.8 tok/s
- 06 B300 288 GB · 8,000 GB/s · Q8_0 24.0 tok/s
- 07 B200 180 GB · 8,000 GB/s · Q8_0 24.0 tok/s
- 08 H100 PCIe 96 GB 96 GB · 3,360 GB/s · Q4_K_M 23.3 tok/s
- 09 H100 SXM5 96 GB 96 GB · 3,360 GB/s · Q4_K_M 23.3 tok/s
- 10 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q5_K_M 22.3 tok/s
The smallest GPUs that still run SaulLM-large
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 H100 CNX 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
- 02 H800 PCIe 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
- 03 H800 SXM5 80 GB · needs 69.6 GB · Q3_K_M · tight 27.2 tok/s
- 04 A800 PCIe 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 15.7 tok/s
- 05 H100 PCIe 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
- 06 H100 SXM5 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 27.2 tok/s
- 07 A800 SXM4 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
- 08 A100 PCIe 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 15.7 tok/s
- 09 A100X 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
- 10 A100 SXM4 80 GB 80 GB · needs 69.6 GB · Q3_K_M · tight 16.5 tok/s
What the numbers mean
What you need to run it
Minimum card
A100 SXM4 80 GB
Memory needed
69.6 GB
Fastest
29.1 tok/s
SaulLM-large sits at 141B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 37 of the cards we track can hold it.
The least hardware that works is a A100 SXM4 80 GB. Its 80 GB is enough at Q3_K_M compression, giving roughly 16.5 tokens per second.
At the other end, a H100 NVL 94 GB generates roughly 29.1 tokens per second on it, on the strength of 3,940 GB/s of memory bandwidth.
What this model is
SaulLM-large was published by Equall.ai, in United States of America, in July 2024. The organisation is categorised as industry.
It works in Language, and is recorded as doing question answering.
Its starting point was Mixtral 8x22B — most models at this scale are adapted from an existing base rather than built from nothing.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.
What decides the speed
Across every card that can run it, the middle of the range is about 16.5 tokens per second, and 35 of them clear the ten tokens per second that roughly matches reading speed.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
Step by step
How to choose a GPU for SaulLM-large
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
The table lists every card that can hold SaulLM-large — around 69.6 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Match the context to your actual use
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for SaulLM-large.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage SaulLM-large by squeezing it further than you would want.
-
04
Sort by speed
Ranking by tokens per second for SaulLM-large follows memory bandwidth, not core counts, which is why the H100 NVL 94 GB tops it at 29.1 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage SaulLM-large from those with room to spare. Buy for the second if the context might grow.
-
06
See what else that card runs
Following a card through to its own page shows every other model it can hold, which is the question that follows once SaulLM-large is settled.
Answers
SaulLM-large — common questions
How fast is SaulLM-large on a GPU?
It depends on the card. The quickest we calculate is a H100 NVL 94 GB at about 29.1 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 35 of the cards that can run SaulLM-large clear that.
How much VRAM does SaulLM-large need?
About 69.6 GB at Q3_K_M compression, which is what the smallest card that runs it uses. Less compression needs more: the figures in the memory column above are recalculated for each card, because each one holds the least-compressed version it can.
Is SaulLM-large open source?
Its weights are published, so SaulLM-large can be downloaded and run on your own hardware. Note that open weights is not the same as open source in the full sense — it says nothing about the training data, the training code, or the commercial terms attached.
How many parameters does SaulLM-large have?
SaulLM-large has 141B parameters. SaulLM-large is based on Mixtral-141B-Instruct, a Transformer model with a Mixture of Experts that selects only 2 out of 8 experts to process tokens for each layer [1]. https://arxiv.org/abs/2407.19584. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.
Who created SaulLM-large?
SaulLM-large was published by Equall.ai, based in United States of America, categorised as industry.
When was SaulLM-large released?
SaulLM-large was published in July 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
What is SaulLM-large used for?
SaulLM-large works in Language, and is recorded as handling question answering. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.
Where can I download SaulLM-large?
The weights for SaulLM-large are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run SaulLM-large if it does not fit in my GPU?
It can be split between the card and system memory, but SaulLM-large generates painfully slowly that way — the nearest miss we calculate is short by 21.2 GB. Nothing on this page assumes offloading.
Would two GPUs run SaulLM-large faster?
A second card roughly doubles the memory available but not the generation rate. With 37 cards already able to run SaulLM-large alone, the case for pairing is weak.
Why does the quantisation differ between cards for SaulLM-large?
Each card is shown running the least-compressed copy it can hold, and SaulLM-large appears at 6 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these SaulLM-large speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 17–47 tok/s on the H100 NVL 94 GB, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run SaulLM-large?
The smallest card in our catalogue that holds SaulLM-large is the A100 SXM4 80 GB, with 80 GB of memory. It runs the model at Q3_K_M using about 69.6 GB, and produces roughly 16.5 tokens per second. 37 cards in total can run it.
The other direction
Looking at it from the other side?
This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.