TRIMELMext (247M) 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 · 149 tok/s
Fastest card
B200
13,718 tok/s · 180 GB
Which GPUs can run TRIMELMext (247M)?
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 | |||||
|---|---|---|---|---|---|---|---|
|
13,718
tok/s
8,231–21,948 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.0 GB | Q8_0 | Comfortable |
|
13,718
tok/s
8,231–21,948 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,954
tok/s
6,572–17,526 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,954
tok/s
6,572–17,526 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
8,760
tok/s
5,256–14,017 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
8,385
tok/s
5,031–13,416 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
8,385
tok/s
5,031–13,416 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
8,025
tok/s
4,815–12,840 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.0 GB | Q8_0 | Comfortable |
|
7,122
tok/s
4,273–11,395 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
7,122
tok/s
4,273–11,395 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
7,122
tok/s
4,273–11,395 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,756
tok/s
4,054–10,809 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,761
tok/s
3,457–9,218 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,761
tok/s
3,457–9,218 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.0 GB | Q8_0 | Comfortable |
|
5,761
tok/s
3,457–9,218 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,761
tok/s
3,457–9,218 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,761
tok/s
3,457–9,218 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
4,387
tok/s
2,632–7,019 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
4,387
tok/s
2,632–7,019 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,656
tok/s
2,193–5,849 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,578
tok/s
2,147–5,724 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,498
tok/s
2,099–5,597 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.0 GB | Q8_0 | Comfortable |
|
3,498
tok/s
2,099–5,597 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,498
tok/s
2,099–5,597 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.0 GB | Q8_0 | Comfortable |
|
3,498
tok/s
2,099–5,597 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.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
- Princeton University
- Organisation type
- Academia
- Country
- United States of America
- Published
- 25 May 2022
- Authors
- Zexuan Zhong, Tao Lei, Danqi Chen
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Translation
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
- 247M
- Training data
- 21,086,208,000 tokens
- Epochs
- 204.72
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.1 × 10¹⁹ FLOP
Table 9: 73728 tokens per update * 286000 updates =21086208000 tokens Using 6ND formula: 6 * 247000000 * 21086208000 = 3.124976e+19
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 (non-commercial)
- Training code
- Open (non-commercial)
code and weights, no clear license: https://github.com/princeton-nlp/TRIME?tab=readme-ov-file
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
- 152
- Benchmark data
- TRIMELMext (247M)
Sources
Where this record came from and when it was last checked.
- Reference
- Training Language Models with Memory Augmentation
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run TRIMELMext (247M)
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 13,718 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 13,718 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 10,954 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 10,954 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 8,760 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 8,385 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 8,385 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 8,025 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 7,122 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 7,122 tok/s
The smallest GPUs that still run TRIMELMext (247M)
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.0 GB · Q8_0 · comfortable 165 tok/s
- 02 RTX A400 4 GB · needs 1.0 GB · Q8_0 · comfortable 165 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.0 GB · Q8_0 · comfortable 219 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.0 GB · Q8_0 · comfortable 329 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.0 GB · Q8_0 · comfortable 58.5 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.0 GB · Q8_0 · comfortable 171 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.0 GB · Q8_0 · comfortable 193 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.0 GB · Q8_0 · comfortable 171 tok/s
- 09 Arc A310 4 GB · needs 1.0 GB · Q8_0 · comfortable 138 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.0 GB · Q8_0 · comfortable 143 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
1.0 GB
Fastest
13,718 tok/s
TRIMELMext (247M) reaches a parameter count of 247M. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 818.
At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 149 tokens per second.
At the other end sits B200, generating roughly 13,718 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Where it came from
TRIMELMext (247M) was published by Princeton University, in the country recorded as United States of America, during May 2022. It comes out of an organisation categorised as academia.
It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Translation.
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.
Understanding the speeds
Half the cards that hold it manage more than 385.2 tokens per second. Producing text faster than most people read it: 818 of them.
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.
Its internal architecture is not on file, so memory is approximated from the parameter count and marked accordingly. Expect the real figure to differ, more so at long context.
How it was trained
Training it took a computation budget of roughly 3.1 × 10¹⁹ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 21,086,208,000 tokens of text.
Step by step
How to choose a GPU for TRIMELMext (247M)
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
Start from what it actually needs, which is the requirement of TRIMELMext (247M), needing around 1.0 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.
-
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 TRIMELMext (247M).
-
03
Choose how far you will compress it
Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q8_0 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.
-
04
Sort by speed
The speed ordering is effectively an ordering by memory bandwidth, for TRIMELMext (247M). It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 13,718 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of TRIMELMext (247M). 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.
-
06
See what else that card runs
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for TRIMELMext (247M).
Answers
TRIMELMext (247M) — common questions
TRIMELMext (247M)— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q8_0, using about 1.0 GB and generating roughly 2,555 tokens per second. The fit is comfortable.
TRIMELMext (247M)— can I run it on a GPU holding 12 GB?
Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 1.0 GB and generating roughly 1,564 tokens per second. The fit is comfortable.
TRIMELMext (247M)— can I run it on a GPU holding 16 GB?
Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 1.0 GB and generating roughly 1,938 tokens per second. The fit is comfortable.
TRIMELMext (247M)— can I run it on a GPU holding 24 GB?
Yes. The card GeForce RTX 5090 D V2, holding 24 GB, runs it at a compression of Q8_0, using about 1.0 GB and generating roughly 2,298 tokens per second. The fit is comfortable.
TRIMELMext (247M)— 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.
TRIMELMext (247M)— how many parameters does it have?
It has a parameter count of 247M. 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.
TRIMELMext (247M)— who created it?
It was published by Princeton University, based in United States of America, an organisation categorised as academia.
TRIMELMext (247M)— when was it released?
It was published in May 2022. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
TRIMELMext (247M)— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Translation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
TRIMELMext (247M)— 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.
TRIMELMext (247M)— how much compute was used to train it?
Training consumed around 3.1 × 10¹⁹ FLOP. 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.
TRIMELMext (247M)— can I run it if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. Every figure here assumes the whole model is resident on the card.
TRIMELMext (247M)— 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: 818. So a second card is rarely the answer here.
TRIMELMext (247M)— why does the quantisation differ between cards?
A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
TRIMELMext (247M)— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 8,231–21,948 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
TRIMELMext (247M)— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q8_0 using about 1.0 GB, and produces roughly 149 tokens per second. The number of cards able to run it in total: 818.
TRIMELMext (247M)— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 13,718 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: 818.
TRIMELMext (247M)— how much VRAM does it need?
It needs about 1.0 GB at a compression of Q8_0, 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.
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.