Ferret (13B) TPS calculator

Open weights Columbia University,Apple 13B parameters October 2023

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

509 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Xeon Phi 5110P

8 GB · Q3_K_M · 18.3 tok/s

Fastest card

B200

261 tok/s · 180 GB

Which GPUs can run Ferret (13B)?

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.

509 cards match

Calculating
Needs Quantisation Fit
261 tok/s

156–417 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 14.6 GB Q8_0 Comfortable
261 tok/s

156–417 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 14.6 GB Q8_0 Comfortable
208 tok/s

125–333 · low confidence

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

125–333 · low confidence

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

100–266 · low confidence

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

96–255 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 14.6 GB Q8_0 Comfortable
159 tok/s

96–255 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 14.6 GB Q8_0 Comfortable
152 tok/s

91–244 · low confidence

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

81–217 · low confidence

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

81–217 · low confidence

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

81–217 · low confidence

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

79–210 · low confidence

CMP 170HX 8 GB NVIDIA 8 GB 1,490 GB/s Sep 2021 7.1 GB Q3_K_M Tight
128 tok/s

77–205 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 14.6 GB Q8_0 Comfortable
117 tok/s

70–188 · low confidence

CMP 170HX 10 GB NVIDIA 10 GB 1,560 GB/s Sep 2021 8.6 GB Q4_K_M Tight
109 tok/s

66–175 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 14.6 GB Q8_0 Comfortable
109 tok/s

66–175 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 14.6 GB Q8_0 Comfortable
109 tok/s

66–175 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 14.6 GB Q8_0 Comfortable
109 tok/s

66–175 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 14.6 GB Q8_0 Comfortable
109 tok/s

66–175 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 14.6 GB Q8_0 Comfortable
83.4 tok/s

50–133 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 14.6 GB Q8_0 Comfortable
83.4 tok/s

50–133 · low confidence

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

42–111 · low confidence

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

41–109 · low confidence

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

41–108 · low confidence

RTX A5000-8Q NVIDIA 8 GB 768 GB/s Apr 2021 7.1 GB Q3_K_M Tight
66.5 tok/s

40–106 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 14.6 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
Columbia University,Apple
Organisation type
Academia,Industry
Country
United States of America
Published
11 October 2023
Authors
Haoxuan You, Haotian Zhang, Zhe Gan, Xianzhi Du, Bowen Zhang, Zirui Wang, Liangliang Cao, Shih-Fu Chang, Yinfei Yang

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Multimodal, Language, Vision
Task
Object recognition, Language modeling
Base model
Vicuna-13B v0
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
13B

13B

Training data
172,649,572 tokens
Epochs
3

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.

Fine-tuning compute
4 × 10¹⁹ FLOP

"The training takes ~5 days on 8 A100 GPU for a Ferret-13B" 5 * 24 * 3600 * 0.3 utilization (assumption) * 312 TFLOP/s = 4.04e19

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
Chips used
8
Chip-hours
960
Wall-clock time
120 hours

"The training takes ∼5/2.5 days on 8 A100 GPU for a Ferret-13B/7B."

Power draw
6.4 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)
Training code
Open (non-commercial)

https://github.com/apple/ml-ferret?tab=License-1-ov-file#readme confusingly, the license page in the repo is permissive and MIT-like, but the README says "The data, and code is intended and licensed for research use only. They are also restricted to uses that follow the license agreement of LLaMA, Vicuna and GPT-4. The dataset is CC BY NC 4.0 (allowing only non-commercial use) and models trained using the dataset should not be used outside of research purposes." train script: https://github.com…

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Why it is tracked
SOTA improvement

claimed SOTA on a new benchmark "To evaluate this new capability, we introduce Ferret-Bench, covering three new types of tasks: Referring Description, Referring Reasoning, and Grounding in Conversation. We benchmark existing MLLMs and observe that Ferret can outperform the best of them by 20.4% on average."

Record confidence
Confident
Citations
524

Sources

Where this record came from and when it was last checked.

Reference
Ferret: Refer and Ground Anything Anywhere at Any Granularity
Last updated
25 May 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Xeon Phi 5110P

Memory needed

7.1 GB

Fastest

261 tok/s

Ferret (13B) is small enough at 13B parameters that hardware is rarely the obstacle — 509 of the cards we track can run it, including cards several years old.

At the low end, a Xeon Phi 5110P handles it — 8 GB, at Q3_K_M, for about 18.3 tokens per second.

Top of the range is the B200, at roughly 261 tokens per second thanks to 8,000 GB/s of bandwidth.

What this model is

Ferret (13B) was published by Columbia University,Apple, in United States of America, in October 2023. academia,Industry is the category the publisher falls under.

It works in Multimodal, Language, Vision, and is recorded as doing object recognition, Language modeling.

It is derived from Vicuna-13B v0 rather than trained from scratch, which is the usual way a specialised model is produced.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.

What decides the speed

The median result is around 21.2 tokens per second; 459 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.

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.

How it was trained

It was trained on about 172,649,572 tokens of text.

It is tracked in the underlying dataset for one reason in particular: sOTA improvement.

Step by step

How to choose a GPU for Ferret (13B)

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

  1. 01

    Start from the memory column

    The table lists every card that can hold Ferret (13B) — around 7.1 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Match the context to your actual use

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

  3. 03

    Choose how far you will compress it

    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 Ferret (13B) by squeezing it further than you would want.

  4. 04

    Compare tokens per second, not specifications

    The speed ordering for Ferret (13B) is effectively an ordering by memory bandwidth, which is why the B200 tops it at 261 tok/s.

  5. 05

    Look at the headroom, not just the fit

    A tight fit runs Ferret (13B) but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.

  6. 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 Ferret (13B) is settled.

Answers

Ferret (13B) — common questions

01

Would two GPUs run Ferret (13B) faster?

Two cards buy memory rather than speed. That matters for Ferret (13B) only if one card cannot hold it — 509 can, so a second adds little.

02

Why does the quantisation differ between cards for Ferret (13B)?

Because capacity varies, so does how hard Ferret (13B) has to be squeezed — 5 distinct levels appear in the table above. Set a minimum quality to compare at one.

03

How accurate are these Ferret (13B) speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 156–417 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

04

What GPU do I need to run Ferret (13B)?

The smallest card in our catalogue that holds Ferret (13B) is the Xeon Phi 5110P, with 8 GB of memory. It runs the model at Q3_K_M using about 7.1 GB, and produces roughly 18.3 tokens per second. 509 cards in total can run it.

05

How fast is Ferret (13B) on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 261 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 459 of the cards that can run Ferret (13B) clear that.

06

How much VRAM does Ferret (13B) need?

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

07

Can I run Ferret (13B) on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q3_K_M, using about 7.1 GB and generating roughly 131 tokens per second — a tight fit.

08

Can I run Ferret (13B) on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q5_K_M, using about 10.1 GB and generating roughly 53.1 tokens per second — a tight fit.

09

Can I run Ferret (13B) on a 16 GB GPU?

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

10

Can I run Ferret (13B) on a 24 GB GPU?

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

11

Is Ferret (13B) open source?

Its weights are published, so Ferret (13B) 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.

12

How many parameters does Ferret (13B) have?

Ferret (13B) has 13B parameters. 13B. 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.

13

Who created Ferret (13B)?

Ferret (13B) was published by Columbia University,Apple, based in United States of America, categorised as academia,Industry.

14

When was Ferret (13B) released?

Ferret (13B) was published in October 2023. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

15

What is Ferret (13B) used for?

Ferret (13B) works in Multimodal, Language, Vision, and is recorded as handling object recognition, Language modeling. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

16

Where can I download Ferret (13B)?

The weights for Ferret (13B) are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

17

Can I run Ferret (13B) if it does not fit in my GPU?

It can be split between the card and system memory, but Ferret (13B) generates painfully slowly that way — the nearest miss we calculate is short by 3.2 GB. Nothing on this page assumes offloading.

Source

Original publication

Record last updated 25 May 2026

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.