Grover-Mega TPS calculator

Open weights University of Washington 1.5B parameters May 2019

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 that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 24.6 tok/s

Fastest card

B200

2,259 tok/s · 180 GB

Which GPUs can run Grover-Mega?

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.

818 cards match

Calculating
Needs Quantisation Fit
2,259 tok/s

1,355–3,614 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 2.3 GB Q8_0 Comfortable
2,259 tok/s

1,355–3,614 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 2.3 GB Q8_0 Comfortable
1,804 tok/s

1,082–2,886 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 2.3 GB Q8_0 Comfortable
1,804 tok/s

1,082–2,886 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 2.3 GB Q8_0 Comfortable
1,443 tok/s

866–2,308 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 2.3 GB Q8_0 Comfortable
1,381 tok/s

828–2,209 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 2.3 GB Q8_0 Comfortable
1,381 tok/s

828–2,209 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 2.3 GB Q8_0 Comfortable
1,321 tok/s

793–2,114 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 2.3 GB Q8_0 Comfortable
1,173 tok/s

704–1,876 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 2.3 GB Q8_0 Comfortable
1,173 tok/s

704–1,876 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 2.3 GB Q8_0 Comfortable
1,173 tok/s

704–1,876 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 2.3 GB Q8_0 Comfortable
1,112 tok/s

667–1,780 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 2.3 GB Q8_0 Comfortable
949 tok/s

569–1,518 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.3 GB Q8_0 Comfortable
949 tok/s

569–1,518 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 2.3 GB Q8_0 Comfortable
949 tok/s

569–1,518 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 2.3 GB Q8_0 Comfortable
949 tok/s

569–1,518 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.3 GB Q8_0 Comfortable
949 tok/s

569–1,518 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 2.3 GB Q8_0 Comfortable
722 tok/s

433–1,156 · low confidence

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

433–1,156 · low confidence

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

361–963 · low confidence

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

353–943 · low confidence

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

346–922 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 2.3 GB Q8_0 Comfortable
576 tok/s

346–922 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 2.3 GB Q8_0 Comfortable
576 tok/s

346–922 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 2.3 GB Q8_0 Comfortable
576 tok/s

346–922 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 2.3 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 Washington
Organisation type
Academia
Country
United States of America
Published
29 May 2019
Authors
R Zellers, A Holtzman, H Rashkin, Y Bisk

What it does

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

Domain
Language
Task
Language modeling/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
1.5B

"Our largest model, Grover-Mega, has 48 layers and 1.5 billion parameters, on par with GPT2"

Training data
32,000,000,000 tokens

"We trained Grover-Mega for 800k iterations, using a batch size of 512 and 256 TPU v3 cores." "We trained each Grover model on randomly-sampled sequences from RealNews with length 1024." "After deduplication, RealNews is 120 gigabytes without compression." 120 GB * 200M English words per GB / 0.75 English words per token = 32000000000 tokens 800000 * 512 * 1024 / 32000000000 ~ 13 epochs

Epochs
13

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

"We trained Grover-Mega for 800k iterations, using a batch size of 512 and 256 TPU v3 cores. Training time was two weeks." TPUv3 is 123 teraflops, but for 2 cores. So 256/2 * 123 teraflops * 14 days * 24 * 3600 * 0.3 (utilization assumption) = 5.7e21 6 FLOP / parameter / token * 1.5 * 10^9 parameters * 800000 steps * 512 [batch size] * 1024 [sequence length] = 3.7748736e+21 FLOP sqrt(5.7e21*3.7748736e+21) = 4.6386183e+21

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

"We trained Grover-Mega for 800k iterations, using a batch size of 512 and 256 TPU v3 cores. Training time was two weeks."

Power draw
118.5 kW
Compute cost
$15,692

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

apache, code and weights: https://github.com/rowanz/grover train code here, inference code in main readme: https://github.com/rowanz/grover/tree/master/lm

How it is classified

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

Frontier model
Yes
Record confidence
Confident
Citations
1,231

Sources

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

Reference
Defending Against Neural Fake News
Last updated
25 May 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

2.3 GB

Fastest

2,259 tok/s

Grover-Mega is small enough at 1.5B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

At the low end, a Tesla C1080 handles it — 4 GB, at Q8_0, for about 24.6 tokens per second.

Top of the range is the B200, at roughly 2,259 tokens per second thanks to 8,000 GB/s of bandwidth.

Where it came from

Grover-Mega was published by University of Washington, in United States of America, in May 2019. It comes out of academia.

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

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.

Understanding the speeds

Across every card that can run it, the middle of the range is about 63.4 tokens per second, and 796 of them clear the ten tokens per second that roughly matches reading speed.

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

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.

How it was trained

The training run consumed about 4.6 × 10²¹ FLOP, on Google TPU v3. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

It was trained on about 32,000,000,000 tokens of text.

Step by step

How to choose a GPU for Grover-Mega

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Start from the memory column

    Look at what Grover-Mega actually needs — around 2.3 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.

  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: at long context Grover-Mega can slip off a card that handles short questions easily.

  3. 03

    Set a quality floor

    Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage Grover-Mega by squeezing it further than you would want.

  4. 04

    Sort by speed

    The speed ordering for Grover-Mega is effectively an ordering by memory bandwidth, which is why the B200 tops it at 2,259 tok/s.

  5. 05

    Check the fit verdict before buying

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

  6. 06

    See what else that card runs

    Following a card through to its own page shows every other model it can hold, which is the question that follows once Grover-Mega is settled.

Answers

Grover-Mega — common questions

01

How much compute was used to train Grover-Mega?

Around 4.6 × 10²¹ FLOP, on Google TPU v3. 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.

02

Can I run Grover-Mega 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 Grover-Mega is rarely worth using. Every figure here assumes the whole model is on the card.

03

Would two GPUs run Grover-Mega faster?

A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run Grover-Mega alone, the case for pairing is weak.

04

Why does the quantisation differ between cards for Grover-Mega?

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

05

How accurate are these Grover-Mega speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 1,355–3,614 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

06

What GPU do I need to run Grover-Mega?

The smallest card in our catalogue that holds Grover-Mega is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 2.3 GB, and produces roughly 24.6 tokens per second. 818 cards in total can run it.

07

How fast is Grover-Mega on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 2,259 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 796 of the cards that can run Grover-Mega clear that.

08

How much VRAM does Grover-Mega need?

About 2.3 GB at Q8_0 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.

09

Can I run Grover-Mega on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 2.3 GB and generating roughly 421 tokens per second — a comfortable fit.

10

Can I run Grover-Mega on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 2.3 GB and generating roughly 258 tokens per second — a comfortable fit.

11

Can I run Grover-Mega on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 2.3 GB and generating roughly 319 tokens per second — a comfortable fit.

12

Can I run Grover-Mega on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 2.3 GB and generating roughly 378 tokens per second — a comfortable fit.

13

Is Grover-Mega open source?

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

14

How many parameters does Grover-Mega have?

Grover-Mega has 1.5B parameters. "Our largest model, Grover-Mega, has 48 layers and 1.5 billion parameters, on par with GPT2". 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.

15

Who created Grover-Mega?

Grover-Mega was published by University of Washington, based in United States of America, categorised as academia.

16

When was Grover-Mega released?

Grover-Mega was published in May 2019. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

17

What is Grover-Mega used for?

Grover-Mega works in Language, and is recorded as handling language modeling/generation. 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.

18

Where can I download Grover-Mega?

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

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.