Tulu V2 DPO 70B TPS calculator

Open weights Allen Institute for AI,University of Washington 70B parameters November 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

61 cards that can run it

818 cards we hold specifications for

Smallest card that fits

A100 PCIe 40 GB

40 GB · Q3_K_M · 25.5 tok/s

Fastest card

B200

48.4 tok/s · 180 GB

Which GPUs can run Tulu V2 DPO 70B?

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
48.4 tok/s

29–77 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 75.6 GB Q8_0 Comfortable
48.4 tok/s

29–77 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 75.6 GB Q8_0 Comfortable
38.7 tok/s

23–62 · low confidence

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

23–62 · low confidence

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

19–49 · low confidence

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

18–47 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 75.6 GB Q8_0 Comfortable
29.6 tok/s

18–47 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 75.6 GB Q8_0 Comfortable
29.5 tok/s

18–47 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 59.3 GB Q6_K Comfortable
29.5 tok/s

18–47 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 59.3 GB Q6_K Comfortable
28.3 tok/s

17–45 · low confidence

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

16–42 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 43.0 GB Q4_K_M Tight
25.5 tok/s

15–41 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 34.9 GB Q3_K_M Tight
25.5 tok/s

15–41 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 34.9 GB Q3_K_M Tight
25.5 tok/s

15–41 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 34.9 GB Q3_K_M Tight
25.1 tok/s

15–40 · low confidence

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

15–40 · low confidence

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

15–40 · low confidence

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

14–38 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 75.6 GB Q8_0 Tight
21.8 tok/s

13–35 · low confidence

H100 SXM5 64 GB NVIDIA 64 GB 2,020 GB/s Mar 2023 51.2 GB Q5_K_M Tight
20.3 tok/s

12–33 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
20.3 tok/s

12–33 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
20.3 tok/s

12–33 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
18.7 tok/s

11–30 · low confidence

RTX PRO 5000 Blackwell NVIDIA 48 GB 1,340 GB/s Mar 2025 43.0 GB Q4_K_M Tight
17.9 tok/s

11–29 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 59.3 GB Q6_K Comfortable
17.9 tok/s

11–29 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 59.3 GB Q6_K 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
Allen Institute for AI,University of Washington
Organisation type
Research collective,Academia
Country
United States of America
Published
20 November 2023
Authors
Hamish Ivison, Yizhong Wang, Valentina Pyatkin, Nathan Lambert, Matthew Peters, Pradeep Dasigi, Joel Jang, David Wadden, Noah A. Smith, Iz Beltagy, Hannaneh Hajishirzi

What it does

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

Domain
Language
Task
Language modeling/generation, Question answering
Base model
Llama 2-70B
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
70B

70B

Training data
tokens

"After filtering, the V2 mixture consists of 326,154 samples" "The mean length of a sample is 1097 tokens" -> total ~ 357 790 938 tokens from figure 1 (more accurate): (1500*10^4.2)+(2500*10^4)+(3500*10^4.2)+(4500*10^4)+(5500*100) = 149 795 000 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.

How it was established
Hardware,Operation counting
Fine-tuning compute
5.7 × 10²¹ FLOP

123000000000000*512*168*3600*0.3*(1 chip / 2 cores)= 5.7131825e+21 6*70*10^9*150000000*3 = 1.89e+20 not sure why here is such a big difference

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
Google TPU v3
Chips used
512
Wall-clock time
168 hours (7 days)

"The 70B variant of TÜLU V2-DPO was trained on a 512-core TPUv3, completing three epochs in approximately 7 days." "All models except QLoRA models were trained on a 256-chip (512-chip for 70B DPO training) TPU v3 pod."

Power draw
457.0 kW
Cloud vendor
Google Cloud

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
Open source

llama license for weights https://huggingface.co/allenai/tulu-2-dpo-70b apache 2.0 for insturction code https://github.com/allenai/open-instruct

How it is classified

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

Record confidence
Likely

Sources

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

Reference
Camels in a Changing Climate: Enhancing LM Adaptation with Tulu 2
Last updated
28 November 2025

The extremes

What the numbers mean

What you need to run it

Minimum card

A100 PCIe 40 GB

Memory needed

34.9 GB

Fastest

48.4 tok/s

Tulu V2 DPO 70B reaches a parameter count of 70B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 61.

The least hardware that works is A100 PCIe 40 GB, with a memory capacity of 40 GB, running it at a compression of Q3_K_M and producing around 25.5 tokens per second.

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

Background

Tulu V2 DPO 70B was published by Allen Institute for AI,University of Washington, in the country recorded as United States of America, during November 2023. It comes out of an organisation categorised as research collective,Academia.

It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Question answering.

Rather than being trained from scratch, it is derived from Llama 2-70B. Most models at this scale are adapted from an existing base rather than built from nothing.

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.

Reading the throughput figures

The median result is around 17.1 tokens per second. Producing text faster than most people read it: 50 of them.

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.

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 Tulu V2 DPO 70B

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

    Start from what it actually needs, which is the requirement of Tulu V2 DPO 70B, needing around 34.9 GB at a compression of Q3_K_M. That figure, not the headline performance of a card, is what decides whether it runs.

  2. 02

    Decide how long your conversations run

    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 Tulu V2 DPO 70B.

  3. 03

    Choose how far you will compress it

    Each card runs the least-compressed copy it can hold, reaching a compression of Q3_K_M 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

    Rank by throughput rather than spec sheet

    Ranking by tokens per second follows memory bandwidth rather than core counts, for Tulu V2 DPO 70B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 48.4 tok/s.

  5. 05

    Read the fit column last

    A tight fit runs, but leaves nothing spare for a longer conversation, in the case of Tulu V2 DPO 70B. 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 Tulu V2 DPO 70B.

Answers

Tulu V2 DPO 70B — common questions

01

Tulu V2 DPO 70B— what GPU do I need to run it?

The smallest card in our catalogue that holds it is A100 PCIe 40 GB, with a memory capacity of 40 GB. It runs the model at a compression of Q3_K_M using about 34.9 GB, and produces roughly 25.5 tokens per second. The number of cards able to run it in total: 61.

02

Tulu V2 DPO 70B— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 48.4 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: 50.

03

Tulu V2 DPO 70B— how much VRAM does it need?

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

04

Tulu V2 DPO 70B— 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.

05

Tulu V2 DPO 70B— how many parameters does it have?

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

06

Tulu V2 DPO 70B— who created it?

It was published by Allen Institute for AI,University of Washington, based in United States of America, an organisation categorised as research collective,Academia.

07

Tulu V2 DPO 70B— when was it released?

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

08

Tulu V2 DPO 70B— what is it used for?

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

09

Tulu V2 DPO 70B— 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.

10

Tulu V2 DPO 70B— can I run it if it does not fit in my GPU?

It can be split between the card and system memory, but it generates painfully slowly that way. The nearest miss we calculate falls short by 14.2 GB. Every figure here assumes the whole model is resident on the card.

11

Tulu V2 DPO 70B— would two GPUs run it faster?

A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 61. So a second card is rarely the answer here.

12

Tulu V2 DPO 70B— 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: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

13

Tulu V2 DPO 70B— how accurate are these speed estimates?

These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 29–77 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

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.