LLaVA-NeXT-34B (LLaVA-1.6) TPS calculator

Open weights University of Wisconsin Madison,ByteDance,Nanyang Technological University,University of California (UC) Berkeley 34.8B parameters January 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

132 cards that can run it

818 cards we hold specifications for

Smallest card that fits

RTX A4500

20 GB · Q3_K_M · 21.1 tok/s

Fastest card

B200

97.5 tok/s · 180 GB

Which GPUs can run LLaVA-NeXT-34B (LLaVA-1.6)?

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.

132 cards match

Calculating
Needs Quantisation Fit
97.5 tok/s

59–156 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 37.9 GB Q8_0 Comfortable
97.5 tok/s

59–156 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 37.9 GB Q8_0 Comfortable
77.9 tok/s

47–125 · low confidence

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

47–125 · low confidence

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

37–100 · low confidence

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

36–95 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 37.9 GB Q8_0 Comfortable
59.6 tok/s

36–95 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 37.9 GB Q8_0 Comfortable
57.0 tok/s

34–91 · low confidence

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

30–81 · low confidence

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

30–81 · low confidence

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

30–81 · low confidence

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

29–77 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 37.9 GB Q8_0 Comfortable
41.0 tok/s

25–66 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 37.9 GB Q8_0 Comfortable
41.0 tok/s

25–66 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 37.9 GB Q8_0 Comfortable
41.0 tok/s

25–66 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 37.9 GB Q8_0 Comfortable
41.0 tok/s

25–66 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 37.9 GB Q8_0 Comfortable
41.0 tok/s

25–66 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 37.9 GB Q8_0 Comfortable
40.7 tok/s

24–65 · low confidence

DRIVE A100 PROD NVIDIA 32 GB 1,870 GB/s May 2020 25.8 GB Q5_K_M Tight
40.7 tok/s

24–65 · low confidence

GRID A100A NVIDIA 32 GB 1,870 GB/s May 2020 25.8 GB Q5_K_M Tight
40.1 tok/s

24–64 · low confidence

GeForce RTX 5090 D V2 NVIDIA 24 GB 1,340 GB/s Aug 2025 19.7 GB IQ4_XS Tight
39.0 tok/s

23–62 · low confidence

GeForce RTX 5090 NVIDIA 32 GB 1,790 GB/s Jan 2025 25.8 GB Q5_K_M Tight
39.0 tok/s

23–62 · low confidence

GeForce RTX 5090 D NVIDIA 32 GB 1,790 GB/s Jan 2025 25.8 GB Q5_K_M Tight
36.5 tok/s

22–58 · low confidence

A30X NVIDIA 24 GB 1,220 GB/s Apr 2021 19.7 GB IQ4_XS Tight
31.2 tok/s

19–50 · low confidence

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

19–50 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 37.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
University of Wisconsin Madison,ByteDance,Nanyang Technological University,University of California (UC) Berkeley
Organisation type
Academia,Industry,Academia,Academia
Country
United States of America, China, Singapore
Published
30 January 2024
Authors
Haotian Liu, Chunyuan Li, Yuheng Li, Bo Li, Yuanhan Zhang, Sheng Shen, Yong Jae Lee

What it does

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

Domain
Multimodal, Language, Vision
Task
Visual question answering, Chat, Question answering

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

34.75B

Training data
89,338,000 tokens

'1318K" image-text pairs

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
2.6 × 10²⁰ FLOP

2.6e20 = 32 * 312e12 * 0.3 * 24* 3600 = num gpus * peak flops * assumed utilization rate * time in seconds "The largest 34B variant finishes training in ~1 day with 32 A100s."

How it was established
Hardware

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
32
Chip-hours
768
Wall-clock time
24 hours

"The largest 34B variant finishes training in ~1 day with 32 A100s."

Power draw
25.3 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 (unrestricted)

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
LLaVA-NeXT: Improved reasoning, OCR, and world knowledge
Last updated
11 February 2026

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

RTX A4500

Memory needed

17.7 GB

Fastest

97.5 tok/s

LLaVA-NeXT-34B (LLaVA-1.6) reaches a parameter count of 34.8B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 132.

The entry point is RTX A4500, with a memory capacity of 20 GB, running it at a compression of Q3_K_M and producing around 21.1 tokens per second.

The quickest result comes from B200, generating roughly 97.5 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

What this model is

LLaVA-NeXT-34B (LLaVA-1.6) was published by University of Wisconsin Madison,ByteDance,Nanyang Technological University,University of California (UC) Berkeley, in the country recorded as United States of America, during January 2024. The category the publisher falls under is academia,Industry,Academia,Academia.

It works in the domain of Multimodal, Language, Vision, and is recorded as performing the task of visual question answering, Chat, Question answering.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.

What decides the speed

Across every card that can run it, the middle of the range sits at 20.7 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 103 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.

Training and provenance

Training it took a computation budget of roughly 2.6 × 10²⁰ FLOP, on hardware recorded as NVIDIA A100. That figure measures what producing the model cost, and has no bearing on how fast it answers.

It was trained on a corpus of about 89,338,000 tokens of text.

Step by step

How to choose a GPU for LLaVA-NeXT-34B (LLaVA-1.6)

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 LLaVA-NeXT-34B (LLaVA-1.6), needing around 17.7 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.

  2. 02

    Set the context length you will work at

    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 LLaVA-NeXT-34B (LLaVA-1.6).

  3. 03

    Choose how far you will compress it

    The quantisation column varies by card, because a bigger card holds a more accurate copy, 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

    Compare tokens per second, not specifications

    Sort by speed to see how cards rank for LLaVA-NeXT-34B (LLaVA-1.6). It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 97.5 tok/s.

  5. 05

    Check the fit verdict before buying

    Tight means it loads and works with no room to raise the context later, in the case of LLaVA-NeXT-34B (LLaVA-1.6). 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

    Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond LLaVA-NeXT-34B (LLaVA-1.6).

Answers

LLaVA-NeXT-34B (LLaVA-1.6) — common questions

01

LLaVA-NeXT-34B (LLaVA-1.6)— how accurate are these speed estimates?

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

02

LLaVA-NeXT-34B (LLaVA-1.6)— what GPU do I need to run it?

The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of Q3_K_M using about 17.7 GB, and produces roughly 21.1 tokens per second. The number of cards able to run it in total: 132.

03

LLaVA-NeXT-34B (LLaVA-1.6)— how fast is it on a GPU?

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

04

LLaVA-NeXT-34B (LLaVA-1.6)— how much VRAM does it need?

It needs about 17.7 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.

05

LLaVA-NeXT-34B (LLaVA-1.6)— 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 IQ4_XS, using about 19.7 GB and generating roughly 40.1 tokens per second. The fit is tight.

06

LLaVA-NeXT-34B (LLaVA-1.6)— 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.

07

LLaVA-NeXT-34B (LLaVA-1.6)— how many parameters does it have?

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

08

LLaVA-NeXT-34B (LLaVA-1.6)— who created it?

It was published by University of Wisconsin Madison,ByteDance,Nanyang Technological University,University of California (UC) Berkeley, based in United States of America, an organisation categorised as academia,Industry,Academia,Academia.

09

LLaVA-NeXT-34B (LLaVA-1.6)— when was it released?

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

10

LLaVA-NeXT-34B (LLaVA-1.6)— what is it used for?

It works in the domain of Multimodal, Language, Vision, and is recorded as handling the task of visual question answering, Chat, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.

11

LLaVA-NeXT-34B (LLaVA-1.6)— 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.

12

LLaVA-NeXT-34B (LLaVA-1.6)— how much compute was used to train it?

Training consumed around 2.6 × 10²⁰ FLOP, on hardware recorded as NVIDIA A100. 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.

13

LLaVA-NeXT-34B (LLaVA-1.6)— 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 7.3 GB. Every figure here assumes the whole model is resident on the card.

14

LLaVA-NeXT-34B (LLaVA-1.6)— 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: 132. So a second card is rarely the answer here.

15

LLaVA-NeXT-34B (LLaVA-1.6)— why does the quantisation differ between cards?

Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 6. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Source

Original publication

Record last updated 11 February 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.