NV-Embed-v2 TPS calculator
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
818 cards we hold specifications for
Smallest card that fits
Tesla K20c
5 GB · Q3_K_M · 28.9 tok/s
Fastest card
B200
484 tok/s · 180 GB
Which GPUs can run NV-Embed-v2?
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 | |||||
|---|---|---|---|---|---|---|---|
|
484
tok/s
290–774 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 8.2 GB | Q8_0 | Comfortable |
|
484
tok/s
290–774 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 8.2 GB | Q8_0 | Comfortable |
|
387
tok/s
232–618 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 8.2 GB | Q8_0 | Comfortable |
|
387
tok/s
232–618 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 8.2 GB | Q8_0 | Comfortable |
|
309
tok/s
185–495 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
296
tok/s
178–473 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 8.2 GB | Q8_0 | Comfortable |
|
296
tok/s
178–473 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 8.2 GB | Q8_0 | Comfortable |
|
283
tok/s
170–453 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
238
tok/s
143–381 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
155
tok/s
93–248 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 8.2 GB | Q8_0 | Comfortable |
|
155
tok/s
93–248 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 8.2 GB | Q8_0 | Comfortable |
|
131
tok/s
79–210 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.6 GB | Q6_K | Tight |
|
129
tok/s
77–206 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
126
tok/s
76–202 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 8.2 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
- NVIDIA
- Organisation type
- Industry
- Country
- United States of America
- Published
- 30 August 2024
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
- Mistral 7B
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
- 7B
- Training data
- tokens
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
- 1 × 10²⁰ FLOP
I assume it is very similar to NV-Embed-v1 and don't see any significant differences. I expect the compute is likely to be the same.
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
Creative Commons Attribution Non Commercial 4.0 https://huggingface.co/nvidia/NV-Embed-v1
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.
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run NV-Embed-v2
Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 484 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 484 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 387 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 387 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 309 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 296 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 296 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 283 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 251 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 251 tok/s
The smallest GPUs that still run NV-Embed-v2
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Quadro P2200 5 GB · needs 4.1 GB · Q3_K_M · tight 27.8 tok/s
- 02 P102-100 5 GB · needs 4.1 GB · Q3_K_M · tight 61.1 tok/s
- 03 GeForce GTX 1060 5 GB 5 GB · needs 4.1 GB · Q3_K_M · tight 22.2 tok/s
- 04 Quadro P2000 5 GB · needs 4.1 GB · Q3_K_M · tight 19.5 tok/s
- 05 Tesla K20s 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 06 Tesla K20m 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 07 Tesla K20c 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 08 RTX 1000 Mobile Ada Generation 6 GB · needs 4.9 GB · Q4_K_M · tight 26.8 tok/s
- 09 GeForce RTX 3050 6 GB 6 GB · needs 4.9 GB · Q4_K_M · tight 23.5 tok/s
- 10 Arc A380M 6 GB · needs 4.9 GB · Q4_K_M · tight 16.9 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla K20c
Memory needed
4.1 GB
Fastest
484 tok/s
NV-Embed-v2 is small enough at 7B parameters that hardware is rarely the obstacle — 589 of the cards we track can run it, including cards several years old.
At the low end, a Tesla K20c handles it — 5 GB, at Q3_K_M, for about 28.9 tokens per second.
A B200 is the fastest we calculate for it: about 484 tokens per second, from 8,000 GB/s of memory bandwidth.
What this model is
NV-Embed-v2 was published by NVIDIA, in United States of America, in August 2024. The organisation is categorised as industry.
It works in Language, and is recorded as doing language modeling/generation, Question answering.
Its starting point was Mistral 7B — most models at this scale are adapted from an existing base rather than built from nothing.
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 26.1 tokens per second; 559 cards produce text faster than most people read it.
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 NV-Embed-v2
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
The table lists every card that can hold NV-Embed-v2 — around 4.1 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Match the context to your actual use
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason NV-Embed-v2 stops fitting a card that seemed fine.
-
03
Choose how far you will compress it
Compression is what makes NV-Embed-v2 fit smaller cards, at some cost in accuracy — Q3_K_M on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Sort by speed
Ranking by tokens per second for NV-Embed-v2 follows memory bandwidth, not core counts, which is why the B200 tops it at 484 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs NV-Embed-v2 but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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 NV-Embed-v2 is settled.
Answers
NV-Embed-v2 — common questions
How many parameters does NV-Embed-v2 have?
NV-Embed-v2 has 7B parameters. 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.
Who created NV-Embed-v2?
NV-Embed-v2 was published by NVIDIA, based in United States of America, categorised as industry.
When was NV-Embed-v2 released?
NV-Embed-v2 was published in August 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.
What is NV-Embed-v2 used for?
NV-Embed-v2 works in Language, and is recorded as handling language modeling/generation, Question answering. 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.
Where can I download NV-Embed-v2?
The weights for NV-Embed-v2 are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run NV-Embed-v2 if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 1.3 GB. Our figures for NV-Embed-v2 assume it is fully resident.
Would two GPUs run NV-Embed-v2 faster?
Two cards buy memory rather than speed. That matters for NV-Embed-v2 only if one card cannot hold it — 589 can, so a second adds little.
Why does the quantisation differ between cards for NV-Embed-v2?
A larger card holds a more accurate copy. Across the cards that run NV-Embed-v2, 4 compression levels are used; the floor control above pins it to one.
How accurate are these NV-Embed-v2 speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 290–774 tok/s on the B200 rather than a single number.
What GPU do I need to run NV-Embed-v2?
The smallest card in our catalogue that holds NV-Embed-v2 is the Tesla K20c, with 5 GB of memory. It runs the model at Q3_K_M using about 4.1 GB, and produces roughly 28.9 tokens per second. 589 cards in total can run it.
How fast is NV-Embed-v2 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 484 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 559 of the cards that can run NV-Embed-v2 clear that.
How much VRAM does NV-Embed-v2 need?
About 4.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.
Can I run NV-Embed-v2 on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q6_K, using about 6.6 GB and generating roughly 131 tokens per second — a tight fit.
Can I run NV-Embed-v2 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 8.2 GB and generating roughly 55.2 tokens per second — a comfortable fit.
Can I run NV-Embed-v2 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 8.2 GB and generating roughly 68.4 tokens per second — a comfortable fit.
Can I run NV-Embed-v2 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 8.2 GB and generating roughly 81.1 tokens per second — a comfortable fit.
Is NV-Embed-v2 open source?
Its weights are published, so NV-Embed-v2 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.
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.