OREAL 32B TPS calculator

Open weights Shanghai AI Lab,Shanghai Jiao Tong University,Chinese University of Hong Kong (CUHK),InnoHK 32B parameters February 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

132 cards that can run it

818 cards we hold specifications for

Smallest card that fits

RTX A4500

20 GB · Q3_K_M · 22.9 tok/s

Fastest card

B200

106 tok/s · 180 GB

Which GPUs can run OREAL 32B?

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
106 tok/s

64–169 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 35.0 GB Q8_0 Comfortable
106 tok/s

64–169 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 35.0 GB Q8_0 Comfortable
84.6 tok/s

51–135 · low confidence

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

51–135 · low confidence

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

41–108 · low confidence

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

39–104 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 35.0 GB Q8_0 Comfortable
64.7 tok/s

39–104 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 35.0 GB Q8_0 Comfortable
61.9 tok/s

37–99 · low confidence

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

33–88 · low confidence

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

33–88 · low confidence

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

33–88 · low confidence

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

31–83 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 35.0 GB Q8_0 Comfortable
44.5 tok/s

27–71 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 35.0 GB Q8_0 Comfortable
44.5 tok/s

27–71 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 35.0 GB Q8_0 Comfortable
44.5 tok/s

27–71 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 35.0 GB Q8_0 Comfortable
44.5 tok/s

27–71 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 35.0 GB Q8_0 Comfortable
44.5 tok/s

27–71 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 35.0 GB Q8_0 Comfortable
40.9 tok/s

25–66 · low confidence

GeForce RTX 5090 D V2 NVIDIA 24 GB 1,340 GB/s Aug 2025 20.1 GB Q4_K_M Tight
37.3 tok/s

22–60 · low confidence

A30X NVIDIA 24 GB 1,220 GB/s Apr 2021 20.1 GB Q4_K_M Tight
36.0 tok/s

22–58 · low confidence

DRIVE A100 PROD NVIDIA 32 GB 1,870 GB/s May 2020 27.5 GB Q6_K Tight
36.0 tok/s

22–58 · low confidence

GRID A100A NVIDIA 32 GB 1,870 GB/s May 2020 27.5 GB Q6_K Tight
34.4 tok/s

21–55 · low confidence

GeForce RTX 5090 NVIDIA 32 GB 1,790 GB/s Jan 2025 27.5 GB Q6_K Tight
34.4 tok/s

21–55 · low confidence

GeForce RTX 5090 D NVIDIA 32 GB 1,790 GB/s Jan 2025 27.5 GB Q6_K Tight
33.9 tok/s

20–54 · low confidence

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

20–54 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 35.0 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
Shanghai AI Lab,Shanghai Jiao Tong University,Chinese University of Hong Kong (CUHK),InnoHK
Organisation type
Academia,Academia,Academia,Government
Country
China, Hong Kong
Published
10 February 2025
Authors
Chengqi Lyu, Songyang Gao, Yuzhe Gu, Wenwei Zhang, Jianfei Gao, Kuikun Liu, Ziyi Wang, Shuaibin Li, Qian Zhao, Haian Huang, Weihan Cao, Jiangning Liu, Hongwei Liu, Junnan Liu, Songyang Zhang, Dahua Lin, Kai Chen

What it does

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

Domain
Mathematics, Language
Task
Mathematical reasoning, Quantitative reasoning, Language modeling/generation, Question answering
Base model
Qwen2.5-32B

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
32B
Training data
tokens

"During training iterations, each batch consists of 64 questions, with 16 rollouts per question. The max length of each rollout trajectory is set to 16384 tokens. Then the correctness of each response is averaged to calculate the pass rate, and questions with an overall pass rate of 0 or 1 are discarded." from https://github.com/InternLM/OREAL 90 steps 90*16384*64*16 = 1509949440 tokens (upper bound since some questions were discarded)

Epochs
1

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.

How it was established
Operation counting
Fine-tuning compute
2.9 × 10²⁰ FLOP

6 FLOP / token / parameter * 32 * 10^ 9 parameters * 1509949440 tokens [see dataset size notes] = 2.8991029e+20 FLOP

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
128
Power draw
100.5 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)
Training code
Open source

apache 2 https://github.com/InternLM/OREAL https://huggingface.co/internlm/OREAL-32B

Hugging Face
internlm

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
Exploring the Limit of Outcome Reward for Learning Mathematical Reasoning
Last updated
28 November 2025

The extremes

What the numbers mean

What it takes to run this model

Minimum card

RTX A4500

Memory needed

16.3 GB

Fastest

106 tok/s

With 32B parameters, OREAL 32B lands in the range a serious desktop card can handle once the weights are compressed. 132 of the cards we track can run it.

The smallest card that holds it is the RTX A4500 with 20 GB, running it at Q3_K_M and producing around 22.9 tokens per second.

At the other end, a B200 generates roughly 106 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.

Background

OREAL 32B was published by Shanghai AI Lab,Shanghai Jiao Tong University,Chinese University of Hong Kong (CUHK),InnoHK, in China, in February 2025. academia,Academia,Academia,Government is the category the publisher falls under.

It works in Mathematics, Language, and is recorded as doing mathematical reasoning, Quantitative reasoning, Language modeling/generation, Question answering.

It is derived from Qwen2.5-32B rather than trained from scratch, which is the usual way a specialised model is produced.

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

Reading the throughput figures

Half the cards that hold it manage more than 20.7 tokens per second, and 103 exceed reading speed outright.

Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.

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 OREAL 32B

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

    The table lists every card that can hold OREAL 32B — around 16.3 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Match the context to your actual use

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for OREAL 32B.

  3. 03

    Choose how far you will compress it

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

  4. 04

    Rank by throughput rather than spec sheet

    Sort by speed to see how cards rank for OREAL 32B. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 106 tok/s.

  5. 05

    Look at the headroom, not just the fit

    The fit column separates cards that just manage OREAL 32B from those with room to spare. Buy for the second if the context might grow.

  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 OREAL 32B is settled.

Answers

OREAL 32B — common questions

01

How much VRAM does OREAL 32B need?

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

02

Can I run OREAL 32B on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q4_K_M, using about 20.1 GB and generating roughly 40.9 tokens per second — a tight fit.

03

Is OREAL 32B open source?

Its weights are published, so OREAL 32B 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.

04

How many parameters does OREAL 32B have?

OREAL 32B has 32B 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.

05

Who created OREAL 32B?

OREAL 32B was published by Shanghai AI Lab,Shanghai Jiao Tong University,Chinese University of Hong Kong (CUHK),InnoHK, based in China, categorised as academia,Academia,Academia,Government.

06

When was OREAL 32B released?

OREAL 32B was published in February 2025.

07

What is OREAL 32B used for?

OREAL 32B works in Mathematics, Language, and is recorded as handling mathematical reasoning, Quantitative reasoning, Language modeling/generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

08

Where can I download OREAL 32B?

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

09

Can I run OREAL 32B if it does not fit in my GPU?

It can be split between the card and system memory, but OREAL 32B generates painfully slowly that way — the nearest miss we calculate is short by 5.7 GB. Nothing on this page assumes offloading.

10

Would two GPUs run OREAL 32B faster?

A second card roughly doubles the memory available but not the generation rate. With 132 cards already able to run OREAL 32B alone, the case for pairing is weak.

11

Why does the quantisation differ between cards for OREAL 32B?

Each card is shown running the least-compressed copy it can hold, and OREAL 32B appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

12

How accurate are these OREAL 32B speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 64–169 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.

13

What GPU do I need to run OREAL 32B?

The smallest card in our catalogue that holds OREAL 32B is the RTX A4500, with 20 GB of memory. It runs the model at Q3_K_M using about 16.3 GB, and produces roughly 22.9 tokens per second. 132 cards in total can run it.

14

How fast is OREAL 32B on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 106 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 103 of the cards that can run OREAL 32B clear that.

Source

Original publication

Record last updated 28 November 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.