Kimi Dev 72b TPS calculator

Open weights Moonshot 72B parameters June 2025

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

61 of 818 cards that can run it

Smallest card that fits

A100 PCIe 40 GB

40 GB · Q3_K_M · 24.8 tok/s

Fastest card

B200

47.1 tok/s · 180 GB

Which GPUs can run Kimi Dev 72b?

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.

61 cards match

Calculating
Needs Quantisation Fit
47.1 tok/s

28–75 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 77.8 GB Q8_0 Comfortable
47.1 tok/s

28–75 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 77.8 GB Q8_0 Comfortable
37.6 tok/s

23–60 · low confidence

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

23–60 · low confidence

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

18–48 · low confidence

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

17–46 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.8 tok/s

17–46 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.7 tok/s

17–46 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 61.0 GB Q6_K Tight
28.7 tok/s

17–46 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 61.0 GB Q6_K Tight
27.5 tok/s

17–44 · low confidence

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

16–43 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 40.1 GB IQ4_XS Tight
24.8 tok/s

15–40 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 35.9 GB Q3_K_M Tight
24.4 tok/s

15–39 · low confidence

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

15–39 · low confidence

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

15–39 · low confidence

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

14–37 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 77.8 GB Q8_0 Tight
21.2 tok/s

13–34 · low confidence

H100 SXM5 64 GB NVIDIA 64 GB 2,020 GB/s Mar 2023 52.6 GB Q5_K_M Tight
19.8 tok/s

12–32 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.4 tok/s

12–31 · low confidence

RTX PRO 5000 Blackwell NVIDIA 48 GB 1,340 GB/s Mar 2025 40.1 GB IQ4_XS Tight
17.4 tok/s

10–28 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 61.0 GB Q6_K Tight
17.4 tok/s

10–28 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 61.0 GB Q6_K 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
Moonshot
Organisation type
Industry
Country
China
Published
16 June 2025

What it does

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

Domain
Language
Task
Code generation
Base model
Qwen2.5-72B

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

72B

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

MIT license: https://huggingface.co/moonshotai/Kimi-Dev-72B

Hugging Face
moonshotai

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
Introducing Kimi-Dev: A Strong and Open-source Coding LLM for Issue Resolution
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

A100 PCIe 40 GB

Memory needed

35.9 GB

Fastest

47.1 tok/s

Kimi Dev 72b sits at 72B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 61 of the cards we track can hold it.

The entry point is the A100 PCIe 40 GB: 40 GB of memory, Q3_K_M compression, roughly 24.8 tokens per second.

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

What this model is

Kimi Dev 72b was published by Moonshot, in China, in June 2025. It comes out of industry.

It works in Language, and is recorded as doing code generation.

It is derived from Qwen2.5-72B rather than trained from scratch, which is the usual way a specialised model is produced.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. It is published under the moonshotai organisation on Hugging Face.

What decides the speed

Across every card that can run it, the middle of the range is about 16.6 tokens per second, and 51 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.

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 Kimi Dev 72b

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

  1. 01

    Check what it needs before anything else

    The table lists every card that can hold Kimi Dev 72b — around 35.9 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 Kimi Dev 72b 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 Kimi Dev 72b by squeezing it further than you would want.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering for Kimi Dev 72b is effectively an ordering by memory bandwidth, which is why the B200 tops it at 47.1 tok/s.

  5. 05

    Read the fit column last

    A tight fit runs Kimi Dev 72b 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

    Following a card through to its own page shows every other model it can hold, which is the question that follows once Kimi Dev 72b is settled.

Answers

Kimi Dev 72b — common questions

01

Where can I download Kimi Dev 72b?

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

02

Can I run Kimi Dev 72b if it does not fit in my GPU?

It can be split between the card and system memory, but Kimi Dev 72b generates painfully slowly that way — the nearest miss we calculate is short by 15.5 GB. Nothing on this page assumes offloading.

03

Would two GPUs run Kimi Dev 72b faster?

Two cards buy memory rather than speed. That matters for Kimi Dev 72b only if one card cannot hold it — 61 can, so a second adds little.

04

Why does the quantisation differ between cards for Kimi Dev 72b?

A larger card holds a more accurate copy. Across the cards that run Kimi Dev 72b, 5 compression levels are used; the floor control above pins it to one.

05

How accurate are these Kimi Dev 72b speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 28–75 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.

06

What GPU do I need to run Kimi Dev 72b?

The smallest card in our catalogue that holds Kimi Dev 72b is the A100 PCIe 40 GB, with 40 GB of memory. It runs the model at Q3_K_M using about 35.9 GB, and produces roughly 24.8 tokens per second. 61 cards in total can run it.

07

How fast is Kimi Dev 72b on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 47.1 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 51 of the cards that can run Kimi Dev 72b clear that.

08

How much VRAM does Kimi Dev 72b need?

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

09

Is Kimi Dev 72b open source?

Its weights are published, so Kimi Dev 72b 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.

10

How many parameters does Kimi Dev 72b have?

Kimi Dev 72b has 72B parameters. 72B. 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.

11

Who created Kimi Dev 72b?

Kimi Dev 72b was published by Moonshot, based in China, categorised as industry.

12

When was Kimi Dev 72b released?

Kimi Dev 72b was published in June 2025.

13

What is Kimi Dev 72b used for?

Kimi Dev 72b works in Language, and is recorded as handling code generation. 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.

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.