Prithvi-EO-2.0 300M TPS calculator

Open weights IBM Research,NASA,University of Alabama,University of Iceland,Forschungszentrum Julich,Virginia Tech (Virginia Polytechnic Institute and State University),Arizona State University,Oregon State University,Boston University,University of California (UC) Berkeley,Julich Supercomputing Center 300M 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

818 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 123 tok/s

Fastest card

B200

11,294 tok/s · 180 GB

Which GPUs can run Prithvi-EO-2.0 300M?

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
11,294 tok/s

6,776–18,071 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.0 GB Q8_0 Comfortable
11,294 tok/s

6,776–18,071 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.0 GB Q8_0 Comfortable
9,019 tok/s

5,411–14,430 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 1.0 GB Q8_0 Comfortable
9,019 tok/s

5,411–14,430 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 1.0 GB Q8_0 Comfortable
7,213 tok/s

4,328–11,540 · low confidence

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

4,142–11,046 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 1.0 GB Q8_0 Comfortable
6,904 tok/s

4,142–11,046 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 1.0 GB Q8_0 Comfortable
6,607 tok/s

3,964–10,571 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 1.0 GB Q8_0 Comfortable
5,864 tok/s

3,518–9,382 · low confidence

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

3,518–9,382 · low confidence

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

3,518–9,382 · low confidence

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

3,337–8,900 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 1.0 GB Q8_0 Comfortable
4,744 tok/s

2,846–7,590 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.0 GB Q8_0 Comfortable
4,744 tok/s

2,846–7,590 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 1.0 GB Q8_0 Comfortable
4,744 tok/s

2,846–7,590 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 1.0 GB Q8_0 Comfortable
4,744 tok/s

2,846–7,590 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.0 GB Q8_0 Comfortable
4,744 tok/s

2,846–7,590 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 1.0 GB Q8_0 Comfortable
3,612 tok/s

2,167–5,779 · low confidence

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

2,167–5,779 · low confidence

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

1,806–4,816 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 1.0 GB Q8_0 Comfortable
2,946 tok/s

1,767–4,713 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 1.0 GB Q8_0 Comfortable
2,880 tok/s

1,728–4,608 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.0 GB Q8_0 Comfortable
2,880 tok/s

1,728–4,608 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.0 GB Q8_0 Comfortable
2,880 tok/s

1,728–4,608 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.0 GB Q8_0 Comfortable
2,880 tok/s

1,728–4,608 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 1.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
IBM Research,NASA,University of Alabama,University of Iceland,Forschungszentrum Julich,Virginia Tech (Virginia Polytechnic Institute and State University),Arizona State University,Oregon State University,Boston University,University of California (UC) Berkeley,Julich Supercomputing Center
Organisation type
Industry,Government,Academia,Academia,Government,Academia,Academia,Academia,Academia,Academia,Government
Country
United States of America, Iceland, Germany
Published
3 February 2025
Authors
Daniela Szwarcman, Sujit Roy, Paolo Fraccaro, Þorsteinn Elí Gíslason, Benedikt Blumenstiel, Rinki Ghosal, Pedro Henrique de Oliveira, Joao Lucas de Sousa Almeida, Rocco Sedona, Yanghui Kang, Srija Chakraborty, Sizhe Wang, Carlos Gomes, Ankur Kumar, Myscon Truong, Denys Godwin, Hyunho Lee, Chia-Yu Hsu, Ata Akbari Asanjan, Besart Mujeci, Disha Shidham, Trevor Keenan, Paulo Arevalo, Wenwen Li, Hamed …

What it does

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

Domain
Earth science

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

300M

Training data
tokens

"Trained on 4.2M global time series samples from NASA’s Harmonized Landsat and Sentinel-2 data archive at 30m resolution" "The models were trained for 400 epochs"

Epochs
400

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

312000000000000 FLOP / GPU / sec [bf16 assumed] * 21000 GPU-hours * 3600 sec / hour * 0.3 [assumed utilization] = 7.07616e+21 FLOP

How it was established
Hardware

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
80
Chip-hours
21,000
Power draw
62.8 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)
Hugging Face
ibm-nasa-geospatial

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
Prithvi-EO-2.0: A Versatile Multi-Temporal Foundation Model for Earth Observation Applications
Last updated
28 November 2025

The extremes

What the numbers mean

What it takes to run this model

Minimum card

Tesla C1080

Memory needed

1.0 GB

Fastest

11,294 tok/s

Prithvi-EO-2.0 300M is small enough at 300M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q8_0 and producing around 123 tokens per second.

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

Where it came from

Prithvi-EO-2.0 300M was published by IBM Research,NASA,University of Alabama,University of Iceland,Forschungszentrum Julich,Virginia Tech (Virginia Polytechnic Institute and State University),Arizona State University,Oregon State University,Boston University,University of California (UC) Berkeley,Julich Supercomputing Center, in United States of America, in February 2025. The organisation is categorised as industry,Government,Academia,Academia,Government,Academia,Academia,Academia,Academia,Academia,Government.

It works in Earth science.

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. It is published under the ibm-nasa-geospatial organisation on Hugging Face.

Understanding the speeds

Across every card that can run it, the middle of the range is about 317.1 tokens per second, and 818 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.

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.

What went into building it

Producing it required around 7.1 × 10²¹ FLOP of arithmetic, on NVIDIA A100, which is a statement about the training budget rather than about inference.

Step by step

How to choose a GPU for Prithvi-EO-2.0 300M

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 Prithvi-EO-2.0 300M — around 1.0 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Set the context length you will work at

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Prithvi-EO-2.0 300M.

  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 Prithvi-EO-2.0 300M by squeezing it further than you would want.

  4. 04

    Rank by throughput rather than spec sheet

    Sort by speed to see how cards rank for Prithvi-EO-2.0 300M. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 11,294 tok/s.

  5. 05

    Look at the headroom, not just the fit

    Tight means Prithvi-EO-2.0 300M loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.

  6. 06

    Open the card you have settled on

    Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Prithvi-EO-2.0 300M.

Answers

Prithvi-EO-2.0 300M — common questions

01

When was Prithvi-EO-2.0 300M released?

Prithvi-EO-2.0 300M was published in February 2025.

02

What is Prithvi-EO-2.0 300M used for?

Prithvi-EO-2.0 300M works in Earth science. These are the areas it was designed around; they describe intent rather than a hard boundary.

03

Where can I download Prithvi-EO-2.0 300M?

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

04

How much compute was used to train Prithvi-EO-2.0 300M?

Around 7.1 × 10²¹ FLOP, on NVIDIA A100. 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.

05

Can I run Prithvi-EO-2.0 300M 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 Prithvi-EO-2.0 300M is rarely worth using. Every figure here assumes the whole model is on the card.

06

Would two GPUs run Prithvi-EO-2.0 300M faster?

Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold Prithvi-EO-2.0 300M on their own, a second card is rarely the answer here.

07

Why does the quantisation differ between cards for Prithvi-EO-2.0 300M?

A larger card holds a more accurate copy. Across the cards that run Prithvi-EO-2.0 300M, 1 compression levels are used; the floor control above pins it to one.

08

How accurate are these Prithvi-EO-2.0 300M speed estimates?

These are estimates with real error bars. The fastest result here, 6,776–18,071 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.

09

What GPU do I need to run Prithvi-EO-2.0 300M?

The smallest card in our catalogue that holds Prithvi-EO-2.0 300M is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.0 GB, and produces roughly 123 tokens per second. 818 cards in total can run it.

10

How fast is Prithvi-EO-2.0 300M on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 11,294 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run Prithvi-EO-2.0 300M clear that.

11

How much VRAM does Prithvi-EO-2.0 300M need?

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

12

Can I run Prithvi-EO-2.0 300M on a 8 GB GPU?

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

13

Can I run Prithvi-EO-2.0 300M on a 12 GB GPU?

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

14

Can I run Prithvi-EO-2.0 300M on a 16 GB GPU?

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

15

Can I run Prithvi-EO-2.0 300M on a 24 GB GPU?

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

16

Is Prithvi-EO-2.0 300M open source?

Its weights are published, so Prithvi-EO-2.0 300M 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.

17

How many parameters does Prithvi-EO-2.0 300M have?

Prithvi-EO-2.0 300M has 300M parameters. 300M. 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.

18

Who created Prithvi-EO-2.0 300M?

Prithvi-EO-2.0 300M was published by IBM Research,NASA,University of Alabama,University of Iceland,Forschungszentrum Julich,Virginia Tech (Virginia Polytechnic Institute and State University),Arizona State University,Oregon State University,Boston University,University of California (UC) Berkeley,Julich Supercomputing Center, based in United States of America, categorised as industry,Government,Academia,Academia,Government,Academia,Academia,Academia,Academia,Academia,Government.

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.