OpenELM-1.1B TPS calculator

Open weights Apple 1.1B parameters May 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

818 of 818 cards that can run it

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 34.1 tok/s

Fastest card

B200

3,137 tok/s · 180 GB

Which GPUs can run OpenELM-1.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
3,137 tok/s

1,882–5,020 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.9 GB Q8_0 Comfortable
3,137 tok/s

1,882–5,020 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.9 GB Q8_0 Comfortable
2,505 tok/s

1,503–4,008 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 1.9 GB Q8_0 Comfortable
2,505 tok/s

1,503–4,008 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 1.9 GB Q8_0 Comfortable
2,004 tok/s

1,202–3,206 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 1.9 GB Q8_0 Comfortable
1,918 tok/s

1,151–3,068 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 1.9 GB Q8_0 Comfortable
1,918 tok/s

1,151–3,068 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 1.9 GB Q8_0 Comfortable
1,835 tok/s

1,101–2,936 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 1.9 GB Q8_0 Comfortable
1,629 tok/s

977–2,606 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 1.9 GB Q8_0 Comfortable
1,629 tok/s

977–2,606 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 1.9 GB Q8_0 Comfortable
1,629 tok/s

977–2,606 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 1.9 GB Q8_0 Comfortable
1,545 tok/s

927–2,472 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
1,318 tok/s

791–2,108 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
1,318 tok/s

791–2,108 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 1.9 GB Q8_0 Comfortable
1,318 tok/s

791–2,108 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
1,318 tok/s

791–2,108 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
1,318 tok/s

791–2,108 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
1,003 tok/s

602–1,605 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 1.9 GB Q8_0 Comfortable
1,003 tok/s

602–1,605 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 1.9 GB Q8_0 Comfortable
836 tok/s

502–1,338 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 1.9 GB Q8_0 Comfortable
818 tok/s

491–1,309 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 1.9 GB Q8_0 Comfortable
800 tok/s

480–1,280 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.9 GB Q8_0 Comfortable
800 tok/s

480–1,280 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.9 GB Q8_0 Comfortable
800 tok/s

480–1,280 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.9 GB Q8_0 Comfortable
800 tok/s

480–1,280 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 1.9 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
1.1B

1.08B (Table 4a)

Training data
tokens

1.5T (Table 4a) Table 9: Batch size (tokens) approx. 4M Training steps 350,000

Epochs
1
Batch size
4,000,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
1.1 × 10²² FLOP

details from Table 4 and Table 9 6 FLOP / token / parameter * 1.08*10^9 parameters * 1.5*10^12 tokens = 9.72e+21 FLOP 312000000000000 FLOP / sec / GPU [bf16 assumed] * 128 GPUs * 11 days * 24 hours / day * 3600 sec / hour * 0.3 [assumed utilization] = 1.1386552e+22 FLOP sqrt(9.72e+21*1.1386552e+22) = 1.0520327e+22

How it was established
Operation counting,Hardware

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
240 hours (10 days)

11 days (Table 9) = 240 hours

Power draw
101.2 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 (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

What the numbers mean

What it takes to run this model

Minimum card

Tesla C1080

Memory needed

1.9 GB

Fastest

3,137 tok/s

OpenELM-1.1B is small enough at 1.1B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q8_0 and producing around 34.1 tokens per second.

The quickest result comes from a B200 at around 3,137 tokens per second — its 8,000 GB/s of bandwidth is what buys that.

What this model is

OpenELM-1.1B 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.

Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all. It is published under the apple organisation on Hugging Face.

What decides the speed

Across every card that can run it, the middle of the range is about 88.1 tokens per second, and 799 of them clear the ten tokens per second that roughly matches reading speed.

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.

What went into building it

Training it took roughly 1.1 × 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-1.1B

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Read the memory figure first

    The table lists every card that can hold OpenELM-1.1B — around 1.9 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Set the context length you will work at

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context OpenELM-1.1B can slip off a card that handles short questions easily.

  3. 03

    Set a quality floor

    The quantisation column varies by card, because a bigger card holds a more accurate copy of OpenELM-1.1B — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.

  4. 04

    Rank by throughput rather than spec sheet

    Sort by speed to see how cards rank for OpenELM-1.1B. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 3,137 tok/s.

  5. 05

    Look at the headroom, not just the fit

    A tight fit runs OpenELM-1.1B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.

  6. 06

    Check the card from the other side

    Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for OpenELM-1.1B alone — a card is usually bought for more than one model.

Answers

OpenELM-1.1B — common questions

01

Can I run OpenELM-1.1B on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.9 GB and generating roughly 525 tokens per second — a comfortable fit.

02

Is OpenELM-1.1B open source?

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

03

How many parameters does OpenELM-1.1B have?

OpenELM-1.1B has 1.1B parameters. 1.08B (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.

04

Who created OpenELM-1.1B?

OpenELM-1.1B was published by Apple, based in United States of America, categorised as industry.

05

When was OpenELM-1.1B released?

OpenELM-1.1B 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.

06

What is OpenELM-1.1B used for?

OpenELM-1.1B works in Language, and is recorded as handling language modeling/generation, Code generation, 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.

07

Where can I download OpenELM-1.1B?

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.

08

How much compute was used to train OpenELM-1.1B?

Around 1.1 × 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.

09

Can I run OpenELM-1.1B 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-1.1B is rarely worth using. Every figure here assumes the whole model is on the card.

10

Would two GPUs run OpenELM-1.1B faster?

Two cards buy memory rather than speed. That matters for OpenELM-1.1B only if one card cannot hold it — 818 can, so a second adds little.

11

Why does the quantisation differ between cards for OpenELM-1.1B?

Because capacity varies, so does how hard OpenELM-1.1B has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.

12

How accurate are these OpenELM-1.1B 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 1,882–5,020 tok/s on the B200 rather than a single number.

13

What GPU do I need to run OpenELM-1.1B?

The smallest card in our catalogue that holds OpenELM-1.1B is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.9 GB, and produces roughly 34.1 tokens per second. 818 cards in total can run it.

14

How fast is OpenELM-1.1B on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 3,137 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 OpenELM-1.1B clear that.

15

How much VRAM does OpenELM-1.1B need?

About 1.9 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.

16

Can I run OpenELM-1.1B on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.9 GB and generating roughly 584 tokens per second — a comfortable fit.

17

Can I run OpenELM-1.1B on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.9 GB and generating roughly 358 tokens per second — a comfortable fit.

18

Can I run OpenELM-1.1B on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.9 GB and generating roughly 443 tokens per second — a comfortable fit.

Source

Original publication

Record last updated 28 November 2025

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.