ConSERT 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
818 cards we hold specifications for
Smallest card that fits
Tesla C1080
4 GB · Q8_0 · 108 tok/s
Fastest card
B200
9,965 tok/s · 180 GB
Which GPUs can run ConSERT?
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 | |||||
|---|---|---|---|---|---|---|---|
|
9,965
tok/s
5,979–15,945 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.1 GB | Q8_0 | Comfortable |
|
9,965
tok/s
5,979–15,945 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.1 GB | Q8_0 | Comfortable |
|
7,958
tok/s
4,775–12,732 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
7,958
tok/s
4,775–12,732 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,364
tok/s
3,818–10,183 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
6,091
tok/s
3,655–9,746 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
6,091
tok/s
3,655–9,746 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,830
tok/s
3,498–9,328 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,174
tok/s
3,104–8,278 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,174
tok/s
3,104–8,278 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,174
tok/s
3,104–8,278 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,908
tok/s
2,945–7,853 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,185
tok/s
2,511–6,697 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,185
tok/s
2,511–6,697 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.1 GB | Q8_0 | Comfortable |
|
4,185
tok/s
2,511–6,697 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,185
tok/s
2,511–6,697 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,185
tok/s
2,511–6,697 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,187
tok/s
1,912–5,099 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
3,187
tok/s
1,912–5,099 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,656
tok/s
1,593–4,249 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,599
tok/s
1,559–4,159 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.1 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.1 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.1 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
- Meituan University,Beijing University of Posts and Telecommunications
- Organisation type
- Academia,Academia
- Country
- China
- Published
- 25 May 2021
- Authors
- Yuanmeng Yan, Rumei Li, Sirui Wang, Fuzheng Zhang, Wei Wu, Weiran Xu
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling
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
- 340M
- Training data
- tokens
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
- 2.8 × 10²⁰ FLOP
- How it was established
- Hardware
Fine-tuning was done using a single Nvidia V100 GPU for a few minutes -> 1.0E+15 to 5.0E+15 (2 to 10 min) Foundation model is BeRT with 2.8e+20 FLOP. So total compute is 2.8e+20.
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 Tesla V100S PCIe 32 GB
- Wall-clock time
- 0 hours
- Compute cost
- $957
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
- Open source
https://github.com/yym6472/ConSERT
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
- Citations
- 633
Sources
Where this record came from and when it was last checked.
- Reference
- ConSERT: A contrastive framework for self-supervised sentence representation transfer
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run ConSERT
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 9,965 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 9,965 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 7,958 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 7,958 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 6,364 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 6,091 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 6,091 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 5,830 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 5,174 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 5,174 tok/s
The smallest GPUs that still run ConSERT
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 1.1 GB · Q8_0 · comfortable 120 tok/s
- 02 RTX A400 4 GB · needs 1.1 GB · Q8_0 · comfortable 120 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.1 GB · Q8_0 · comfortable 159 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.1 GB · Q8_0 · comfortable 239 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.1 GB · Q8_0 · comfortable 42.5 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.1 GB · Q8_0 · comfortable 124 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.1 GB · Q8_0 · comfortable 140 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.1 GB · Q8_0 · comfortable 124 tok/s
- 09 Arc A310 4 GB · needs 1.1 GB · Q8_0 · comfortable 100 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.1 GB · Q8_0 · comfortable 104 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
1.1 GB
Fastest
9,965 tok/s
ConSERT is small enough at 340M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 108 tokens per second.
The quickest result comes from a B200 at around 9,965 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
ConSERT was published by Meituan University,Beijing University of Posts and Telecommunications, in China, in May 2021. The organisation is categorised as academia,Academia.
It works in Language, and is recorded as doing language modeling.
The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold.
Reading the throughput figures
Half the cards that hold it manage more than 279.8 tokens per second, and 818 exceed reading speed outright.
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.
Training and provenance
Training it took roughly 2.8 × 10²⁰ FLOP of computation, on NVIDIA Tesla V100S PCIe 32 GB — a measure of what producing the model cost, not of how fast it answers.
Step by step
How to choose a GPU for ConSERT
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 ConSERT — around 1.1 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Decide how long your conversations run
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for ConSERT.
-
03
Set a quality floor
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage ConSERT by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for ConSERT. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 9,965 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage ConSERT 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 ConSERT is settled.
Answers
ConSERT — common questions
Can I run ConSERT on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,137 tokens per second — a comfortable fit.
Can I run ConSERT on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,408 tokens per second — a comfortable fit.
Can I run ConSERT on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,669 tokens per second — a comfortable fit.
Is ConSERT open source?
Its weights are published, so ConSERT 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 ConSERT have?
ConSERT has 340M parameters. 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 ConSERT?
ConSERT was published by Meituan University,Beijing University of Posts and Telecommunications, based in China, categorised as academia,Academia.
When was ConSERT released?
ConSERT was published in May 2021. 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 ConSERT used for?
ConSERT works in Language, and is recorded as handling language modeling. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download ConSERT?
The weights for ConSERT are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train ConSERT?
Around 2.8 × 10²⁰ FLOP, on NVIDIA Tesla V100S PCIe 32 GB. 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 ConSERT if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down. Our figures for ConSERT assume it is fully resident.
Would two GPUs run ConSERT faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run ConSERT alone, the case for pairing is weak.
Why does the quantisation differ between cards for ConSERT?
A larger card holds a more accurate copy. Across the cards that run ConSERT, 1 compression levels are used; the floor control above pins it to one.
How accurate are these ConSERT speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 5,979–15,945 tok/s on the B200 rather than a single number.
What GPU do I need to run ConSERT?
The smallest card in our catalogue that holds ConSERT is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.1 GB, and produces roughly 108 tokens per second. 818 cards in total can run it.
How fast is ConSERT on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 9,965 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run ConSERT clear that.
How much VRAM does ConSERT need?
About 1.1 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 ConSERT on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,856 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.