Incoder-6.7B TPS calculator

Open weights Facebook AI Research,University of Washington,University of California (UC) Berkeley,Carnegie Mellon University (CMU),Toyota Technological Institute at Chicago 6.7B parameters April 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

589 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla K20c

5 GB · IQ4_XS · 27.4 tok/s

Fastest card

B200

506 tok/s · 180 GB

Which GPUs can run Incoder-6.7B?

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.

589 cards match

Calculating
Needs Quantisation Fit
506 tok/s

303–809 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 7.9 GB Q8_0 Comfortable
506 tok/s

303–809 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 7.9 GB Q8_0 Comfortable
404 tok/s

242–646 · low confidence

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

242–646 · low confidence

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

194–517 · low confidence

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

185–495 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 7.9 GB Q8_0 Comfortable
309 tok/s

185–495 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 7.9 GB Q8_0 Comfortable
296 tok/s

178–473 · low confidence

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

158–420 · low confidence

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

158–420 · low confidence

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

158–420 · low confidence

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

149–399 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 7.9 GB Q8_0 Comfortable
212 tok/s

127–340 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 7.9 GB Q8_0 Comfortable
212 tok/s

127–340 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 7.9 GB Q8_0 Comfortable
212 tok/s

127–340 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 7.9 GB Q8_0 Comfortable
212 tok/s

127–340 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 7.9 GB Q8_0 Comfortable
212 tok/s

127–340 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 7.9 GB Q8_0 Comfortable
162 tok/s

97–259 · low confidence

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

97–259 · low confidence

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

82–219 · low confidence

CMP 170HX 8 GB NVIDIA 8 GB 1,490 GB/s Sep 2021 6.3 GB Q6_K Tight
135 tok/s

81–216 · low confidence

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

79–211 · low confidence

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

77–206 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 7.9 GB Q8_0 Comfortable
129 tok/s

77–206 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 7.9 GB Q8_0 Comfortable
129 tok/s

77–206 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 7.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
Facebook AI Research,University of Washington,University of California (UC) Berkeley,Carnegie Mellon University (CMU),Toyota Technological Institute at Chicago
Organisation type
Industry,Academia,Academia,Academia,Academia
Country
United States of America, France
Published
9 April 2023
Authors
Daniel Fried, Armen Aghajanyan, Jessy Lin, Sida Wang, Eric Wallace, Freda Shi, Ruiqi Zhong, Wen-tau Yih, Luke Zettlemoyer, Mike Lewis

What it does

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

Domain
Language
Task
Code generation

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

6.7B

Training data
52,000,000,000 tokens

216 GB: "Our final pre-training corpus contains a total of 159 GB of code, 52 GB of it in Python, and a total of 57 GB of content from StackOverflow"

Epochs
1

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
3 × 10²¹ FLOP

per table 5, required 3 zettaflop (3e21) to train. also, "INCODER-6.7B was trained on 248 V100 GPUs for 24 days" hardware method: 125 trillion * 248 * 24 * 24 * 3600 * 0.3 = 2e22. suggests their utilization was quite low, or 24 days was just calendar time.

How it was established
Reported

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 V100
Wall-clock time
576 hours (24 days)

24

Compute cost
$3,129

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
Unreleased

CC-BY-NC 4.0 (non commercial) data is open: "To train our models, we collect a corpus of (1) public code with permissive, non-copyleft, opensource licenses from GitHub and GitLab and (2) StackOverflow questions, answers, and comments." inference code, not training code in this repo: https://github.com/dpfried/incoder/blob/main/README.md

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

"Zero-shot infilling with bidirectional context substantially outperforms approaches based on left-to-right-only models, and on several tasks obtains performance comparable to state-of-the-art models fine-tuned on the tasks" I don't see on which benchmarks they claim absolute SOTA

Record confidence
Confident
Citations
864

Sources

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

Reference
InCoder: A Generative Model for Code Infilling and Synthesis
Last updated
25 May 2026

The extremes

What the numbers mean

What you need to run it

Minimum card

Tesla K20c

Memory needed

4.4 GB

Fastest

506 tok/s

Incoder-6.7B reaches a parameter count of 6.7B. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 589.

The least hardware that works is Tesla K20c, with a memory capacity of 5 GB, running it at a compression of IQ4_XS and producing around 27.4 tokens per second.

At the other end sits B200, generating roughly 506 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Where it came from

Incoder-6.7B was published by Facebook AI Research,University of Washington,University of California (UC) Berkeley,Carnegie Mellon University (CMU),Toyota Technological Institute at Chicago, in the country recorded as United States of America, during April 2023. The publishing organisation is categorised as industry,Academia,Academia,Academia,Academia.

It works in the domain of Language, and is recorded as performing the task of code generation.

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.

Understanding the speeds

Half the cards that hold it manage more than 27.3 tokens per second. Producing text faster than most people read it: 562 of them.

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.

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.

How it was trained

The training run consumed about 3 × 10²¹ FLOP, on hardware recorded as NVIDIA V100. That figure measures what producing the model cost, and has no bearing on how fast it answers.

The training set ran to roughly 52,000,000,000 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 Incoder-6.7B

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

    Start from what it actually needs, which is the requirement of Incoder-6.7B, needing around 4.4 GB at a compression of IQ4_XS. No amount of processing power compensates for a card that cannot hold it.

  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, because at long context a card that handles short questions easily can be dropped by Incoder-6.7B.

  3. 03

    Choose how far you will compress it

    Each card runs the least-compressed copy it can hold, reaching a compression of IQ4_XS on the smallest card that fits. Setting a minimum quality drops the cards that only manage it by squeezing further than you would want, and holds the comparison at one level.

  4. 04

    Sort by speed

    The speed ordering is effectively an ordering by memory bandwidth, for Incoder-6.7B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 506 tok/s.

  5. 05

    Look at the headroom, not just the fit

    The fit column separates cards that just manage it from those with room to spare, in the case of Incoder-6.7B. Comfortable means you can grow the context later. That difference matters more than a few tokens per second, so buy for comfortable if you expect to.

  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 you have settled on Incoder-6.7B.

Answers

Incoder-6.7B — common questions

01

Incoder-6.7B— where can I download it?

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

02

Incoder-6.7B— how much compute was used to train it?

Training consumed around 3 × 10²¹ FLOP, on hardware recorded as NVIDIA V100. 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.

03

Incoder-6.7B— can I run it 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 model is rarely worth using. The nearest miss we calculate falls short by 1.2 GB. Every figure here assumes the whole model is resident on the card.

04

Incoder-6.7B— would two GPUs run it faster?

Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 589. So a second card is rarely the answer here.

05

Incoder-6.7B— why does the quantisation differ between cards?

A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

06

Incoder-6.7B— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 303–809 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

07

Incoder-6.7B— what GPU do I need to run it?

The smallest card in our catalogue that holds it is Tesla K20c, with a memory capacity of 5 GB. It runs the model at a compression of IQ4_XS using about 4.4 GB, and produces roughly 27.4 tokens per second. The number of cards able to run it in total: 589.

08

Incoder-6.7B— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 506 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and the number of cards clearing that: 562.

09

Incoder-6.7B— how much VRAM does it need?

It needs about 4.4 GB at a compression of IQ4_XS, 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.

10

Incoder-6.7B— can I run it on a GPU holding 8 GB?

Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q6_K, using about 6.3 GB and generating roughly 137 tokens per second. The fit is tight.

11

Incoder-6.7B— can I run it on a GPU holding 12 GB?

Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 7.9 GB and generating roughly 57.7 tokens per second. The fit is comfortable.

12

Incoder-6.7B— can I run it on a GPU holding 16 GB?

Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 7.9 GB and generating roughly 71.4 tokens per second. The fit is comfortable.

13

Incoder-6.7B— can I run it on a GPU holding 24 GB?

Yes. The card GeForce RTX 5090 D V2, holding 24 GB, runs it at a compression of Q8_0, using about 7.9 GB and generating roughly 84.7 tokens per second. The fit is comfortable.

14

Incoder-6.7B— is it open source?

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

15

Incoder-6.7B— how many parameters does it have?

It has a parameter count of 6.7B. 6.7B. 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.

16

Incoder-6.7B— who created it?

It was published by Facebook AI Research,University of Washington,University of California (UC) Berkeley,Carnegie Mellon University (CMU),Toyota Technological Institute at Chicago, based in United States of America, an organisation categorised as industry,Academia,Academia,Academia,Academia.

17

Incoder-6.7B— when was it released?

It was published in April 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.

18

Incoder-6.7B— what is it used for?

It works in the domain of Language, and is recorded as handling the task of code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.

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.