SaulLM-large TPS calculator

Open weights Equall.ai 141B parameters July 2024

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

37 cards that can run it

818 cards we hold specifications for

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

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

Training data
tokens

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

Batch size
4

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%

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.

Power draw
378.7 kW

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

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 reaches a parameter count of 141B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 37.

The least hardware that works is A100 SXM4 80 GB, with a memory capacity of 80 GB, running it at a compression of Q3_K_M and producing around 16.5 tokens per second.

At the other end sits H100 NVL 94 GB, generating roughly 29.1 tokens per second on the strength of a memory bandwidth of 3,940 GB/s.

What this model is

SaulLM-large was published by Equall.ai, in the country recorded as United States of America, during July 2024. The publishing organisation is categorised as industry.

It works in the domain of Language, and is recorded as performing the task of question answering.

Its starting point was an existing base model, Mixtral 8x22B. That is the usual way a specialised model is produced.

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 sits at 16.5 tokens per second. Producing text faster than most people read it: 35 of them.

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.

  1. 01

    Check what it needs before anything else

    The table lists every card able to hold SaulLM-large, needing around 69.6 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.

  2. 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.

  3. 03

    Choose how far you will compress it

    Each card runs the least-compressed copy it can hold, reaching a compression of Q3_K_M on the smallest card that fits. Setting a minimum quality drops the cards that only manage it by squeezing further than you would want, and holds the comparison at one level.

  4. 04

    Sort by speed

    Ranking by tokens per second follows memory bandwidth rather than core counts, for SaulLM-large. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is H100 NVL 94 GB, at 29.1 tok/s.

  5. 05

    Check the fit verdict before buying

    The fit column separates cards that just manage it from those with room to spare, in the case of SaulLM-large. Comfortable means you can grow the context later. That difference matters more than a few tokens per second, so buy for comfortable if you expect to.

  6. 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 you have settled on SaulLM-large.

Answers

SaulLM-large — common questions

01

SaulLM-large— how fast is it on a GPU?

It depends on the card. The quickest we calculate is 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 the number of cards clearing that: 35.

02

SaulLM-large— how much VRAM does it need?

It needs about 69.6 GB at a compression of Q3_K_M, 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.

03

SaulLM-large— is it open source?

Its weights are published, so it 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.

04

SaulLM-large— how many parameters does it have?

It has a parameter count of 141B. 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.

05

SaulLM-large— who created it?

It was published by Equall.ai, based in United States of America, an organisation categorised as industry.

06

SaulLM-large— when was it released?

It 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.

07

SaulLM-large— what is it used for?

It works in the domain of Language, and is recorded as handling the task of 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.

08

SaulLM-large— where can I download it?

The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

09

SaulLM-large— can I run it if it does not fit in my GPU?

It can be split between the card and system memory, but it generates painfully slowly that way. The nearest miss we calculate falls short by 21.2 GB. Every figure here assumes the whole model is resident on the card.

10

SaulLM-large— would two GPUs run it faster?

A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 37. So a second card is rarely the answer here.

11

SaulLM-large— why does the quantisation differ between cards?

Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 6. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

12

SaulLM-large— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 17–47 tok/s on H100 NVL 94 GB. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

13

SaulLM-large— what GPU do I need to run it?

The smallest card in our catalogue that holds it is A100 SXM4 80 GB, with a memory capacity of 80 GB. It runs the model at a compression of Q3_K_M using about 69.6 GB, and produces roughly 16.5 tokens per second. The number of cards able to run it in total: 37.

Source

Original publication

Record last updated 25 May 2026

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.