OpenELM-270M 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 · 137 tok/s
Fastest card
B200
12,549 tok/s · 180 GB
Which GPUs can run OpenELM-270M?
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 | |||||
|---|---|---|---|---|---|---|---|
|
12,549
tok/s
7,529–20,078 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.0 GB | Q8_0 | Comfortable |
|
12,549
tok/s
7,529–20,078 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,021
tok/s
6,012–16,033 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,021
tok/s
6,012–16,033 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
8,014
tok/s
4,808–12,823 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
7,671
tok/s
4,602–12,273 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
7,671
tok/s
4,602–12,273 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
7,341
tok/s
4,405–11,746 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.0 GB | Q8_0 | Comfortable |
|
6,515
tok/s
3,909–10,424 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,515
tok/s
3,909–10,424 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,515
tok/s
3,909–10,424 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,180
tok/s
3,708–9,889 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,271
tok/s
3,162–8,433 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,271
tok/s
3,162–8,433 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.0 GB | Q8_0 | Comfortable |
|
5,271
tok/s
3,162–8,433 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,271
tok/s
3,162–8,433 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,271
tok/s
3,162–8,433 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
4,013
tok/s
2,408–6,421 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
4,013
tok/s
2,408–6,421 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,344
tok/s
2,007–5,351 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,273
tok/s
1,964–5,237 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,200
tok/s
1,920–5,120 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.0 GB | Q8_0 | Comfortable |
|
3,200
tok/s
1,920–5,120 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,200
tok/s
1,920–5,120 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.0 GB | Q8_0 | Comfortable |
|
3,200
tok/s
1,920–5,120 · 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
- Apple
- Organisation type
- Industry
- Country
- United States of America
- Published
- 2 May 2024
- Authors
- Sachin Mehta, Mohammad Hossein Sekhavat, Qingqing Cao, Maxwell Horton, Yanzi Jin, Chenfan Sun, Iman Mirzadeh, Mahyar Najibi, Dmitry Belenko, Peter Zatloukal, Mohammad Rastegari
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Code generation, Question answering
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
- 270M
- Training data
- tokens
- Epochs
- 1
- Batch size
- 4,000,000
0.27B (Table 4a)
1.5T (Table 4a) Table 9: Batch size (tokens) approx. 4M Training steps 350,000
Table 9
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.7 × 10²¹ FLOP
- How it was established
- Operation counting,Hardware
details from Table 4 and Table 9 6 FLOP / token / parameter * 0.27*10^9 parameters * 1.5*10^12 tokens = 2.43e+21 FLOP 312000000000000 FLOP / sec / GPU [bf16 assumed] * 128 GPUs * 3 days * 24 hours / day * 3600 sec / hour * 0.3 [assumed utilization] = 3.1054234e+21 FLOP sqrt(2.43e+21*3.1054234e+21) = 2.7470309e+21
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 A100 SXM4 80 GB
- Chips used
- 128
- Wall-clock time
- 72 hours
- Power draw
- 101.2 kW
3 days (Table 9) = 72 hours
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)
- Hugging Face
- apple
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
- OpenELM: An Efficient Language Model Family with Open Training and Inference Framework
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run OpenELM-270M
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 12,549 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 12,549 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 10,021 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 10,021 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 8,014 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 7,671 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 7,671 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 7,341 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 6,515 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 6,515 tok/s
The smallest GPUs that still run OpenELM-270M
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 151 tok/s
- 02 RTX A400 4 GB · needs 1.0 GB · Q8_0 · comfortable 151 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.0 GB · Q8_0 · comfortable 201 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.0 GB · Q8_0 · comfortable 301 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.0 GB · Q8_0 · comfortable 53.5 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.0 GB · Q8_0 · comfortable 157 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.0 GB · Q8_0 · comfortable 176 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.0 GB · Q8_0 · comfortable 157 tok/s
- 09 Arc A310 4 GB · needs 1.0 GB · Q8_0 · comfortable 126 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.0 GB · Q8_0 · comfortable 131 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
1.0 GB
Fastest
12,549 tok/s
OpenELM-270M is small enough at 270M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q8_0 compression, giving roughly 137 tokens per second.
At the other end, a B200 generates roughly 12,549 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
About this model
OpenELM-270M was published by Apple, in United States of America, in May 2024. It comes out of industry.
It works in Language, and is recorded as doing language modeling/generation, Code generation, Question answering.
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. It is published under the apple organisation on Hugging Face.
How fast it runs, and why
The median result is around 352.4 tokens per second; 818 cards produce text faster than most people read it.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
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.
What went into building it
Training it took roughly 2.7 × 10²¹ FLOP of computation, on NVIDIA A100 SXM4 80 GB — a measure of what producing the model cost, not of how fast it answers.
Step by step
How to choose a GPU for OpenELM-270M
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
Every card here has been checked against OpenELM-270M — around 1.0 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason OpenELM-270M stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
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 OpenELM-270M by squeezing it further than you would want.
-
04
Sort by speed
The speed ordering for OpenELM-270M is effectively an ordering by memory bandwidth, which is why the B200 tops it at 12,549 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs OpenELM-270M but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
Open the card you have settled on
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond OpenELM-270M.
Answers
OpenELM-270M — common questions
Who created OpenELM-270M?
OpenELM-270M was published by Apple, based in United States of America, categorised as industry.
When was OpenELM-270M released?
OpenELM-270M was published in May 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 OpenELM-270M used for?
OpenELM-270M works in Language, and is recorded as handling language modeling/generation, Code generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download OpenELM-270M?
Its weights are published under the apple 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 OpenELM-270M?
Around 2.7 × 10²¹ FLOP, on NVIDIA A100 SXM4 80 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 OpenELM-270M if it does not fit in my GPU?
Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded OpenELM-270M is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run OpenELM-270M faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run OpenELM-270M alone, the case for pairing is weak.
Why does the quantisation differ between cards for OpenELM-270M?
Each card is shown running the least-compressed copy it can hold, and OpenELM-270M appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these OpenELM-270M speed estimates?
These are estimates with real error bars. The fastest result here, 7,529–20,078 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 OpenELM-270M?
The smallest card in our catalogue that holds OpenELM-270M is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.0 GB, and produces roughly 137 tokens per second. 818 cards in total can run it.
How fast is OpenELM-270M on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 12,549 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 OpenELM-270M clear that.
How much VRAM does OpenELM-270M need?
About 1.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 OpenELM-270M on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.0 GB and generating roughly 2,337 tokens per second — a comfortable fit.
Can I run OpenELM-270M on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.0 GB and generating roughly 1,431 tokens per second — a comfortable fit.
Can I run OpenELM-270M on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.0 GB and generating roughly 1,773 tokens per second — a comfortable fit.
Can I run OpenELM-270M on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.0 GB and generating roughly 2,102 tokens per second — a comfortable fit.
Is OpenELM-270M open source?
Its weights are published, so OpenELM-270M 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 OpenELM-270M have?
OpenELM-270M has 270M parameters. 0.27B (Table 4a). 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.
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.