dots.llm1 TPS calculator

Open weights Rednote 142B parameters July 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

37 of 818 cards that can run it

Smallest card that fits

A100 SXM4 80 GB

80 GB · Q3_K_M · 16.4 tok/s

Fastest card

H100 NVL 94 GB

28.9 tok/s · 94 GB

Which GPUs can run dots.llm1?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

37 cards match

Calculating

					Needs	Quantisation	Fit
28.9 tok/s 17–46 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	78.3 GB	IQ4_XS	Tight
27.2 tok/s 16–44 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	103.1 GB	Q5_K_M	Tight
27.0 tok/s 16–43 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	70.1 GB	Q3_K_M	Tight
27.0 tok/s 16–43 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	70.1 GB	Q3_K_M	Tight
24.6 tok/s 15–39 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	78.3 GB	IQ4_XS	Tight
24.6 tok/s 15–39 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	78.3 GB	IQ4_XS	Tight
24.6 tok/s 15–39 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	78.3 GB	IQ4_XS	Tight
23.9 tok/s 14–38 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	152.7 GB	Q8_0	Tight
23.9 tok/s 14–38 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	152.7 GB	Q8_0	Comfortable
22.1 tok/s 13–35 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	103.1 GB	Q5_K_M	Tight
21.2 tok/s 13–34 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	119.7 GB	Q6_K	Tight
21.2 tok/s 13–34 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	119.7 GB	Q6_K	Tight
19.1 tok/s 11–30 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	152.7 GB	Q8_0	Comfortable
19.1 tok/s 11–30 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	152.7 GB	Q8_0	Comfortable
16.4 tok/s 10–26 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	70.1 GB	Q3_K_M	Tight
16.4 tok/s 10–26 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	70.1 GB	Q3_K_M	Tight
16.4 tok/s 10–26 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	70.1 GB	Q3_K_M	Tight
16.4 tok/s 10–26 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	70.1 GB	Q3_K_M	Tight
16.4 tok/s 10–26 · low confidence	H100 PCIe 80 GB NVIDIA	80 GB	2,040 GB/s	Oct 2022	70.1 GB	Q3_K_M	Tight
16.4 tok/s 10–26 · low confidence	H800 PCIe 80 GB NVIDIA	80 GB	2,040 GB/s	Mar 2023	70.1 GB	Q3_K_M	Tight
15.6 tok/s 9–25 · low confidence	A100 PCIe 80 GB NVIDIA	80 GB	1,940 GB/s	Jun 2021	70.1 GB	Q3_K_M	Tight
15.6 tok/s 9–25 · low confidence	A800 PCIe 80 GB NVIDIA	80 GB	1,940 GB/s	Nov 2022	70.1 GB	Q3_K_M	Tight
14.0 tok/s 8–22 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	152.7 GB	Q8_0	Comfortable
13.6 tok/s 8–22 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	103.1 GB	Q5_K_M	Tight
13.6 tok/s 8–22 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	103.1 GB	Q5_K_M	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: Rednote
Organisation type: Industry
Country: China
Published: 6 July 2025
Authors: Bi Huo, Bin Tu, Cheng Qin, Da Zheng, Debing Zhang, Dongjie Zhang, En Li, Fu Guo, Jian Yao, Jie Lou, Junfeng Tian, Li Hu, Ran Zhu, Shengdong Chen, Shuo Liu, Su Guang, Te Wo, Weijun Zhang, Xiaoming Shi, Xinxin Peng, Xing Wu, Yawen Liu, Yuqiu Ji, Ze Wen, Zhenhai Liu, Zichao Li, Zilong Liao

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

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: 142B
Training data: 11,328,000,000,000 tokens
Batch size: 128,000,000

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: 1.2 × 10²⁴ FLOP
How it was established: Hardware,Operation counting

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 H800 SXM5
Chip-hours: 1,456,000

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
Hugging Face: rednote-hilab

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: dots.llm1 Technical Report
Last updated: 19 December 2025

The extremes

The ten fastest GPUs for dots.llm1

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.

The smallest GPUs that still run dots.llm1

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

Hardware requirements in practice

Minimum card

A100 SXM4 80 GB

Memory needed

70.1 GB

Fastest

28.9 tok/s

dots.llm1 sits at 142B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 37 of the cards we track can hold it.

The entry point is the A100 SXM4 80 GB: 80 GB of memory, Q3_K_M compression, roughly 16.4 tokens per second.

A H100 NVL 94 GB is the fastest we calculate for it: about 28.9 tokens per second, from 3,940 GB/s of memory bandwidth.

Background

dots.llm1 was published by Rednote, in China, in July 2025. industry is the category the publisher falls under.

It works in Language, and is recorded as doing language modeling/generation, Question answering.

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 rednote-hilab organisation on Hugging Face.

Reading the throughput figures

The median result is around 16.4 tokens per second; 35 cards produce text faster than most people read it.

Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.

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

The training run consumed about 1.2 × 10²⁴ FLOP, on NVIDIA H800 SXM5. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

It was trained on about 11,328,000,000,000 tokens of text.

Step by step

How to choose a GPU for dots.llm1

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

Look at what dots.llm1 actually needs — around 70.1 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
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 dots.llm1 stops fitting a card that seemed fine.
03

Set a quality floor

The quantisation column varies by card, because a bigger card holds a more accurate copy of dots.llm1 — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.
04

Compare tokens per second, not specifications

The speed ordering for dots.llm1 is effectively an ordering by memory bandwidth, which is why the H100 NVL 94 GB tops it at 28.9 tok/s.
05

Check the fit verdict before buying

A tight fit runs dots.llm1 but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
06

Check the card from the other side

Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond dots.llm1.

Answers

dots.llm1 — common questions

Who created dots.llm1?

dots.llm1 was published by Rednote, based in China, categorised as industry.

When was dots.llm1 released?

dots.llm1 was published in July 2025.

What is dots.llm1 used for?

dots.llm1 works in Language, and is recorded as handling language modeling/generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

Where can I download dots.llm1?

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

How much compute was used to train dots.llm1?

Around 1.2 × 10²⁴ FLOP, on NVIDIA H800 SXM5. 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.

Can I run dots.llm1 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 21.8 GB. Our figures for dots.llm1 assume it is fully resident.

Would two GPUs run dots.llm1 faster?

A second card roughly doubles the memory available but not the generation rate. With 37 cards already able to run dots.llm1 alone, the case for pairing is weak.

Why does the quantisation differ between cards for dots.llm1?

Because capacity varies, so does how hard dots.llm1 has to be squeezed — 5 distinct levels appear in the table above. Set a minimum quality to compare at one.

How accurate are these dots.llm1 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 17–46 tok/s on the H100 NVL 94 GB rather than a single number.

What GPU do I need to run dots.llm1?

The smallest card in our catalogue that holds dots.llm1 is the A100 SXM4 80 GB, with 80 GB of memory. It runs the model at Q3_K_M using about 70.1 GB, and produces roughly 16.4 tokens per second. 37 cards in total can run it.

How fast is dots.llm1 on a GPU?

It depends on the card. The quickest we calculate is a H100 NVL 94 GB at about 28.9 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 35 of the cards that can run dots.llm1 clear that.

How much VRAM does dots.llm1 need?

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

Is dots.llm1 open source?

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

How many parameters does dots.llm1 have?

dots.llm1 has 142B parameters. a large-scale MoE model that activates 14 billion parameters out of a total of 142 billion 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.

Source

Original publication

Record last updated 19 December 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.

All AI models