Pleias-RAG-1B 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
Tesla C1080
4 GB · Q8_0 · 30.7 tok/s
Fastest card
B200
2,824 tok/s · 180 GB
Which GPUs can run Pleias-RAG-1B?
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.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
2,824
tok/s
1,694–4,518 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 2.0 GB | Q8_0 | Comfortable |
|
2,824
tok/s
1,694–4,518 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 2.0 GB | Q8_0 | Comfortable |
|
2,255
tok/s
1,353–3,607 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.0 GB | Q8_0 | Comfortable |
|
2,255
tok/s
1,353–3,607 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.0 GB | Q8_0 | Comfortable |
|
1,803
tok/s
1,082–2,885 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,726
tok/s
1,036–2,761 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.0 GB | Q8_0 | Comfortable |
|
1,726
tok/s
1,036–2,761 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.0 GB | Q8_0 | Comfortable |
|
1,652
tok/s
991–2,643 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 2.0 GB | Q8_0 | Comfortable |
|
1,466
tok/s
880–2,346 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,466
tok/s
880–2,346 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,466
tok/s
880–2,346 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,391
tok/s
834–2,225 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,186
tok/s
712–1,897 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,186
tok/s
712–1,897 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 2.0 GB | Q8_0 | Comfortable |
|
1,186
tok/s
712–1,897 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,186
tok/s
712–1,897 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
|
1,186
tok/s
712–1,897 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
|
903
tok/s
542–1,445 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.0 GB | Q8_0 | Comfortable |
|
903
tok/s
542–1,445 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.0 GB | Q8_0 | Comfortable |
|
752
tok/s
451–1,204 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 2.0 GB | Q8_0 | Comfortable |
|
736
tok/s
442–1,178 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 2.0 GB | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 2.0 GB | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 2.0 GB | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 2.0 GB | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 2.0 GB | Q8_0 | Comfortable |
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
- PleIAs
- Organisation type
- Industry
- Country
- France
- Published
- 25 April 2025
- Authors
- Pierre-Carl Langlais, Pavel Chizhov, Mattia Nee, Carlos Rosas Hinostroza, Matthieu Delsart, Irène Girard, Othman Hicheur, Anastasia Stasenko, Ivan P. Yamshchikov
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Retrieval-augmented generation, Language modeling/generation, Question answering, Search, Text summarization, Translation
- Base model
- Pleias 1.0 1.2B
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
- 1.2B
- Training data
- tokens
- Epochs
- 2
1.2B
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.
- Training compute
- 3 × 10²² FLOP
- How it was established
- Operation counting
- Fine-tuning compute
- 1.4 × 10²⁰ FLOP
base model compute 2.9770787e+22 FLOP + finetune compute 1.3639673e+20 FLOP = 2.9907184e+22 FLOP
6 FLOP / parameter / token * 1.2 * 10^9 parameters * 9471995091 tokens * 2 epochs = 1.3639673e+20 FLOP
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
- NVIDIA H100 SXM5 80GB
- Chips used
- 16
- Power draw
- 22.0 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)
- Training code
- Unreleased
- Hugging Face
- PleIAs
Apache 2.0 https://huggingface.co/PleIAs/Pleias-RAG-1B
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- Even Small Reasoners Should Quote Their Sources: Introducing the Pleias-RAG Model Family
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs for Pleias-RAG-1B
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 B300 288 GB · 8,000 GB/s · Q8_0 2,824 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,824 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,255 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,255 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,803 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,726 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,726 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,652 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,466 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,466 tok/s
The smallest GPUs that still run Pleias-RAG-1B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 2.0 GB · Q8_0 · comfortable 33.9 tok/s
- 02 RTX A400 4 GB · needs 2.0 GB · Q8_0 · comfortable 33.9 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 2.0 GB · Q8_0 · comfortable 45.2 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 2.0 GB · Q8_0 · comfortable 67.8 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 2.0 GB · Q8_0 · comfortable 12.0 tok/s
- 06 Radeon RX 6450M 4 GB · needs 2.0 GB · Q8_0 · comfortable 35.2 tok/s
- 07 Radeon RX 6550M 4 GB · needs 2.0 GB · Q8_0 · comfortable 39.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 2.0 GB · Q8_0 · comfortable 35.2 tok/s
- 09 Arc A310 4 GB · needs 2.0 GB · Q8_0 · comfortable 28.5 tok/s
- 10 Arc Pro A30M 4 GB · needs 2.0 GB · Q8_0 · comfortable 29.4 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
2.0 GB
Fastest
2,824 tok/s
Pleias-RAG-1B is small enough at 1.2B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
At the low end, a Tesla C1080 handles it — 4 GB, at Q8_0, for about 30.7 tokens per second.
At the other end, a B200 generates roughly 2,824 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
What this model is
Pleias-RAG-1B was published by PleIAs, in France, in April 2025. The organisation is categorised as industry.
It works in Language, and is recorded as doing retrieval-augmented generation, Language modeling/generation, Question answering, Search, Text summarization, Translation.
Its starting point was Pleias 1.0 1.2B — most models at this scale are adapted from an existing base rather than built from nothing.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. It is published under the PleIAs organisation on Hugging Face.
What decides the speed
The median result is around 79.3 tokens per second; 799 cards produce text faster than most people read it.
It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.
Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.
How it was trained
Training it took roughly 3 × 10²² FLOP of computation, on NVIDIA H100 SXM5 80GB — a measure of what producing the model cost, not of how fast it answers.
Step by step
How to choose a GPU for Pleias-RAG-1B
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
The table lists every card that can hold Pleias-RAG-1B — around 2.0 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Pleias-RAG-1B.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy of Pleias-RAG-1B — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Sort by speed
Ranking by tokens per second for Pleias-RAG-1B follows memory bandwidth, not core counts, which is why the B200 tops it at 2,824 tok/s.
-
05
Read the fit column last
Tight means Pleias-RAG-1B loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.
-
06
Check the card from the other side
Following a card through to its own page shows every other model it can hold, which is the question that follows once Pleias-RAG-1B is settled.
Answers
Pleias-RAG-1B — common questions
Can I run Pleias-RAG-1B on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 2.0 GB and generating roughly 322 tokens per second — a comfortable fit.
Can I run Pleias-RAG-1B on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 2.0 GB and generating roughly 399 tokens per second — a comfortable fit.
Can I run Pleias-RAG-1B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 2.0 GB and generating roughly 473 tokens per second — a comfortable fit.
Is Pleias-RAG-1B open source?
Its weights are published, so Pleias-RAG-1B 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 Pleias-RAG-1B have?
Pleias-RAG-1B has 1.2B parameters. 1.2B. 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 Pleias-RAG-1B?
Pleias-RAG-1B was published by PleIAs, based in France, categorised as industry.
When was Pleias-RAG-1B released?
Pleias-RAG-1B was published in April 2025.
What is Pleias-RAG-1B used for?
Pleias-RAG-1B works in Language, and is recorded as handling retrieval-augmented generation, Language modeling/generation, Question answering, Search, Text summarization, Translation. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download Pleias-RAG-1B?
Its weights are published under the PleIAs organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train Pleias-RAG-1B?
Around 3 × 10²² FLOP, on NVIDIA H100 SXM5 80GB. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.
Can I run Pleias-RAG-1B if it does not fit in my GPU?
It can be split between the card and system memory, but Pleias-RAG-1B generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run Pleias-RAG-1B faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run Pleias-RAG-1B alone, the case for pairing is weak.
Why does the quantisation differ between cards for Pleias-RAG-1B?
Each card is shown running the least-compressed copy it can hold, and Pleias-RAG-1B appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these Pleias-RAG-1B speed estimates?
These are estimates with real error bars. The fastest result here, 1,694–4,518 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run Pleias-RAG-1B?
The smallest card in our catalogue that holds Pleias-RAG-1B is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 2.0 GB, and produces roughly 30.7 tokens per second. 818 cards in total can run it.
How fast is Pleias-RAG-1B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 2,824 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 799 of the cards that can run Pleias-RAG-1B clear that.
How much VRAM does Pleias-RAG-1B need?
About 2.0 GB at Q8_0 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.
Can I run Pleias-RAG-1B on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 2.0 GB and generating roughly 526 tokens per second — a comfortable fit.
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.