Jamba 1.5 Mini TPS calculator

Open weights AI21 Labs 52B parameters August 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

93 of 818 cards that can run it

Smallest card that fits

Radeon PRO V710

28 GB · Q3_K_M · 37.4 tok/s

Fastest card

B200

282 tok/s · 180 GB

Which GPUs can run Jamba 1.5 Mini?

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.

93 cards match

Calculating
Needs Quantisation Fit
282 tok/s

169–452 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 55.4 GB Q8_0 Comfortable
282 tok/s

169–452 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 55.4 GB Q8_0 Comfortable
225 tok/s

135–361 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 55.4 GB Q8_0 Comfortable
225 tok/s

135–361 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 55.4 GB Q8_0 Comfortable
180 tok/s

108–289 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 55.4 GB Q8_0 Comfortable
173 tok/s

104–276 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 55.4 GB Q8_0 Comfortable
173 tok/s

104–276 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 55.4 GB Q8_0 Comfortable
165 tok/s

99–264 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 55.4 GB Q8_0 Comfortable
162 tok/s

97–259 · low confidence

DRIVE A100 PROD NVIDIA 32 GB 1,870 GB/s May 2020 28.1 GB IQ4_XS Tight
162 tok/s

97–259 · low confidence

GRID A100A NVIDIA 32 GB 1,870 GB/s May 2020 28.1 GB IQ4_XS Tight
155 tok/s

93–248 · low confidence

GeForce RTX 5090 NVIDIA 32 GB 1,790 GB/s Jan 2025 28.1 GB IQ4_XS Tight
155 tok/s

93–248 · low confidence

GeForce RTX 5090 D NVIDIA 32 GB 1,790 GB/s Jan 2025 28.1 GB IQ4_XS Tight
147 tok/s

88–235 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 55.4 GB Q8_0 Comfortable
147 tok/s

88–235 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 55.4 GB Q8_0 Comfortable
147 tok/s

88–235 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 55.4 GB Q8_0 Comfortable
139 tok/s

83–222 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 55.4 GB Q8_0 Comfortable
127 tok/s

76–203 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 31.2 GB Q4_K_M Tight
127 tok/s

76–203 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 31.2 GB Q4_K_M Tight
127 tok/s

76–203 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 31.2 GB Q4_K_M Tight
119 tok/s

71–190 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 55.4 GB Q8_0 Comfortable
119 tok/s

71–190 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 55.4 GB Q8_0 Comfortable
119 tok/s

71–190 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 55.4 GB Q8_0 Comfortable
119 tok/s

71–190 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 55.4 GB Q8_0 Comfortable
119 tok/s

71–190 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 55.4 GB Q8_0 Comfortable
118 tok/s

71–189 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 37.2 GB Q5_K_M Tight

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
AI21 Labs
Organisation type
Industry
Country
Israel
Published
22 August 2024
Authors
Barak Lenz, Alan Arazi, Amir Bergman, Avshalom Manevich, Barak Peleg, Ben Aviram, Chen Almagor, Clara Fridman, Dan Padnos, Daniel Gissin, Daniel Jannai, Dor Muhlgay, Dor Zimberg, Edden M Gerber, Elad Dolev, Eran Krakovsky, Erez Safahi, Erez Schwartz, Gal Cohen, Gal Shachaf, Haim Rozenblum, Hofit Bata, Ido Blass, Inbal Magar, Itay Dalmedigos, Jhonathan Osin, Julie Fadlon, Maria Rozman, Matan Danos,…

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, Question answering
Numerical format
BF16

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
52B

12B active/52B total

Training data
tokens

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 (restricted use)
Training code
Unreleased

Commercial use allowed up to $50M USD annual revenue. https://huggingface.co/ai21labs/AI21-Jamba-1.5-Mini

Hugging Face
ai21labs

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
Jamba-1.5: Hybrid Transformer-Mamba Models at Scale
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Radeon PRO V710

Memory needed

25.1 GB

Fastest

282 tok/s

With 52B parameters, Jamba 1.5 Mini lands in the range a serious desktop card can handle once the weights are compressed. 93 of the cards we track can run it.

The entry point is the Radeon PRO V710: 28 GB of memory, Q3_K_M compression, roughly 37.4 tokens per second.

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

Background

Jamba 1.5 Mini was published by AI21 Labs, in Israel, in August 2024. The organisation is categorised as industry.

It works in Language, and is recorded as doing language modeling/generation, Translation, 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 ai21labs organisation on Hugging Face.

Reading the throughput figures

Half the cards that hold it manage more than 72.0 tokens per second, and 89 exceed reading speed outright.

Because it routes each token through a subset of its weights, it produces text at the pace of a much smaller model. The catch is memory: all of it still has to fit, so the speed is a bonus rather than a discount on hardware.

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.

Step by step

How to choose a GPU for Jamba 1.5 Mini

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

    Every card here has been checked against Jamba 1.5 Mini — around 25.1 GB at Q3_K_M. Capacity is the gate — a card either holds it or it does not.

  2. 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 Jamba 1.5 Mini stops fitting a card that seemed fine.

  3. 03

    Decide how much compression you will accept

    Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage Jamba 1.5 Mini by squeezing it further than you would want.

  4. 04

    Sort by speed

    The speed ordering for Jamba 1.5 Mini is effectively an ordering by memory bandwidth, which is why the B200 tops it at 282 tok/s.

  5. 05

    Check the fit verdict before buying

    A tight fit runs Jamba 1.5 Mini but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.

  6. 06

    Open the card you have settled on

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

Answers

Jamba 1.5 Mini — common questions

01

How many parameters does Jamba 1.5 Mini have?

Jamba 1.5 Mini has 52B parameters. 12B active/52B total. 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.

02

Who created Jamba 1.5 Mini?

Jamba 1.5 Mini was published by AI21 Labs, based in Israel, categorised as industry.

03

When was Jamba 1.5 Mini released?

Jamba 1.5 Mini was published in August 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.

04

What is Jamba 1.5 Mini used for?

Jamba 1.5 Mini works in Language, and is recorded as handling language modeling/generation, Translation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.

05

Where can I download Jamba 1.5 Mini?

Its weights are published under the ai21labs organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.

06

Can I run Jamba 1.5 Mini 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 Jamba 1.5 Mini is rarely worth using — the nearest miss we calculate is short by 9.6 GB. Every figure here assumes the whole model is on the card.

07

Would two GPUs run Jamba 1.5 Mini faster?

A second card roughly doubles the memory available but not the generation rate. With 93 cards already able to run Jamba 1.5 Mini alone, the case for pairing is weak.

08

Why does the quantisation differ between cards for Jamba 1.5 Mini?

Each card is shown running the least-compressed copy it can hold, and Jamba 1.5 Mini appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

09

How accurate are these Jamba 1.5 Mini speed estimates?

These are estimates with real error bars. The fastest result here, 169–452 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.

10

What GPU do I need to run Jamba 1.5 Mini?

The smallest card in our catalogue that holds Jamba 1.5 Mini is the Radeon PRO V710, with 28 GB of memory. It runs the model at Q3_K_M using about 25.1 GB, and produces roughly 37.4 tokens per second. 93 cards in total can run it.

11

How fast is Jamba 1.5 Mini on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 282 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 89 of the cards that can run Jamba 1.5 Mini clear that.

12

How much VRAM does Jamba 1.5 Mini need?

About 25.1 GB at Q3_K_M 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.

13

Is Jamba 1.5 Mini open source?

Its weights are published, so Jamba 1.5 Mini 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.

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.