AWD-LSTM-DRILL + dynamic evaluation† (WT2) TPS calculator

Open weights IDIAP 34M 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 · 1,084 tok/s

Fastest card

B200

99,654 tok/s · 180 GB

Which GPUs can run AWD-LSTM-DRILL + dynamic evaluation† (WT2)?

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
99,654 tok/s

59,792–159,446 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 0.7 GB Q8_0 Comfortable
99,654 tok/s

59,792–159,446 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 0.7 GB Q8_0 Comfortable
79,576 tok/s

47,746–127,322 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 0.7 GB Q8_0 Comfortable
79,576 tok/s

47,746–127,322 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 0.7 GB Q8_0 Comfortable
63,642 tok/s

38,185–101,826 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 0.7 GB Q8_0 Comfortable
60,913 tok/s

36,548–97,462 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 0.7 GB Q8_0 Comfortable
60,913 tok/s

36,548–97,462 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 0.7 GB Q8_0 Comfortable
58,298 tok/s

34,979–93,276 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 0.7 GB Q8_0 Comfortable
51,739 tok/s

31,043–82,783 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 0.7 GB Q8_0 Comfortable
51,739 tok/s

31,043–82,783 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 0.7 GB Q8_0 Comfortable
51,739 tok/s

31,043–82,783 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 0.7 GB Q8_0 Comfortable
49,080 tok/s

29,448–78,527 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 0.7 GB Q8_0 Comfortable
41,855 tok/s

25,113–66,967 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 0.7 GB Q8_0 Comfortable
41,855 tok/s

25,113–66,967 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 0.7 GB Q8_0 Comfortable
41,855 tok/s

25,113–66,967 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 0.7 GB Q8_0 Comfortable
41,855 tok/s

25,113–66,967 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 0.7 GB Q8_0 Comfortable
41,855 tok/s

25,113–66,967 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 0.7 GB Q8_0 Comfortable
31,869 tok/s

19,122–50,991 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 0.7 GB Q8_0 Comfortable
31,869 tok/s

19,122–50,991 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 0.7 GB Q8_0 Comfortable
26,558 tok/s

15,935–42,492 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 0.7 GB Q8_0 Comfortable
25,991 tok/s

15,595–41,586 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 0.7 GB Q8_0 Comfortable
25,412 tok/s

15,247–40,659 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 0.7 GB Q8_0 Comfortable
25,412 tok/s

15,247–40,659 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 0.7 GB Q8_0 Comfortable
25,412 tok/s

15,247–40,659 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 0.7 GB Q8_0 Comfortable
25,412 tok/s

15,247–40,659 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 0.7 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
IDIAP
Organisation type
Academia
Country
Switzerland
Published
14 May 2019
Authors
Nikolaos Pappas, James Henderson

What it does

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

Domain
Language
Task
Language modeling
Numerical format
FP32

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
34M

34M, Table 2

Training data
2,000,000 tokens

max epochs - 1000 (from http://github.com/idiap/drill)

Epochs
1,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
4.1 × 10¹⁷ FLOP

6 FLOP / parameter / token * 34000000 parameters * 2000000 tokens * 1000 epochs = 4.08e+17 FLOP

How it was established
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.

Wall-clock time
29 hours

106 sec per epoch (Table 3) -> 106000 seconds = 29 hours

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

copyleft license (restricts derivative works to be open) https://github.com/idiap/drill?tab=GPL-3.0-1-ov-file#readme train/eval script: https://github.com/idiap/drill/blob/master/main.py

How it is classified

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

Why it is tracked
SOTA improvement

"our models improve over the state-of-the-art by +1.6 perplexity on PennTreebank and by +3.9 perplexity on Wikitext-2"

Record confidence
Likely
Citations
7
Benchmark data
AWD-LSTM-DRILL + dynamic evaluation† (WT2)

Sources

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

Reference
Deep Residual Output Layers for Neural Language Generation
Last updated
11 February 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

0.7 GB

Fastest

99,654 tok/s

AWD-LSTM-DRILL + dynamic evaluation† (WT2) reaches a parameter count of 34M. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 818.

At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 1,084 tokens per second.

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

About this model

AWD-LSTM-DRILL + dynamic evaluation† (WT2) was published by IDIAP, in the country recorded as Switzerland, during May 2019. The category the publisher falls under is academia.

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

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.

How fast it runs, and why

The median result is around 2,798.3 tokens per second. Exceeding reading speed outright: 818 of them.

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.

How it was trained

Producing it required arithmetic totalling around 4.1 × 10¹⁷ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 2,000,000 tokens of text.

The reason it appears in this catalogue at all: sOTA improvement.

Step by step

How to choose a GPU for AWD-LSTM-DRILL + dynamic evaluation† (WT2)

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

    Every card here has been checked against AWD-LSTM-DRILL + dynamic evaluation† (WT2), needing around 0.7 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.

  2. 02

    Decide how long your conversations run

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for AWD-LSTM-DRILL + dynamic evaluation† (WT2).

  3. 03

    Set a quality floor

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

    Sort by speed

    The speed ordering is effectively an ordering by memory bandwidth, for AWD-LSTM-DRILL + dynamic evaluation† (WT2). It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 99,654 tok/s.

  5. 05

    Look at the headroom, not just the fit

    A tight fit runs, but leaves nothing spare for a longer conversation, in the case of AWD-LSTM-DRILL + dynamic evaluation† (WT2). 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

    Check the card from the other side

    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 AWD-LSTM-DRILL + dynamic evaluation† (WT2).

Answers

AWD-LSTM-DRILL + dynamic evaluation† (WT2) — common questions

01

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— who created it?

It was published by IDIAP, based in Switzerland, an organisation categorised as academia.

02

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— when was it released?

It 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.

03

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— what is it used for?

It works in the domain of Language, and is recorded as handling the task of language modeling. 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.

04

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— 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.

05

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— how much compute was used to train it?

Training consumed around 4.1 × 10¹⁷ FLOP. 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.

06

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— can I run it if it does not fit in my GPU?

Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. Every figure here assumes the whole model is resident on the card.

07

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— would two GPUs run it faster?

Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 818. So a second card is rarely the answer here.

08

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

09

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— how accurate are these speed estimates?

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

10

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— what GPU do I need to run it?

The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q8_0 using about 0.7 GB, and produces roughly 1,084 tokens per second. The number of cards able to run it in total: 818.

11

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— how fast is it on a GPU?

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

12

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— how much VRAM does it need?

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

13

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— can I run it on a GPU holding 8 GB?

Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 18,561 tokens per second. The fit is comfortable.

14

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— can I run it on a GPU holding 12 GB?

Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 11,366 tokens per second. The fit is comfortable.

15

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— can I run it on a GPU holding 16 GB?

Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 14,076 tokens per second. The fit is comfortable.

16

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— 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 Q8_0, using about 0.7 GB and generating roughly 16,692 tokens per second. The fit is comfortable.

17

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— 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.

18

AWD-LSTM-DRILL + dynamic evaluation† (WT2)— how many parameters does it have?

It has a parameter count of 34M. 34M, Table 2. 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 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.