Calculate the TPS of the Data Center GPU Max 1550 on local AI models

Intel 128 GB HBM2e 3,280 GB/s January 2023

Every model in our catalogue assessed against this card at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from this card's memory bandwidth and the size of each model once compressed.

Calculated for this card

658 models it can run

721 models in our catalogue altogether

Largest model it holds

Solar Open2 250B

250.3B · Q3_K_M · 54.1 tok/s

Fastest model

Gemma 3 QAT 1B

903 tok/s · 1B

Which AI models can run on a Data Center GPU Max 1550?

Set the inputs, read the answer

More context means more memory for the conversation cache. Speed is for a fresh conversation and does not change with this setting.

Hides models that would only fit by being compressed below this point.

658 models match

Calculating
Quantisation Fit
903 tok/s

542–1,445 · low confidence

Gemma 3 1B 1B Mar 2025 1.8 GB 33k tokens Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

Gemma 3 QAT 1B 1B Apr 2025 1.8 GB 33k tokens Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

HGRN 1B (WT 103) 1B Nov 2023 1.8 GB 131k tokens ? Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

LLama 3..2 Typhoon 2 1B 1B Dec 2024 1.8 GB 131k tokens ? Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

OLMo-1B 1B Feb 2024 1.8 GB 131k tokens ? Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

Pythia-1b 1B Apr 2023 1.8 GB 131k tokens ? Q8_0 Comfortable
836 tok/s

502–1,338 · low confidence

OpenELM-1.1B 1.1B May 2024 1.9 GB 131k tokens ? Q8_0 Comfortable
821 tok/s

493–1,313 · low confidence

DeciCoder-1B 1.1B Aug 2023 1.9 GB 131k tokens ? Q8_0 Comfortable
821 tok/s

493–1,313 · low confidence

SantaCoder 1.1B Jan 2023 1.9 GB 131k tokens ? Q8_0 Comfortable
821 tok/s

493–1,313 · low confidence

TinyLlama-1.1B (1T token checkpoint) 1.1B Oct 2023 1.9 GB 131k tokens ? Q8_0 Comfortable
821 tok/s

493–1,313 · low confidence

TinyLlama-1.1B (3T token checkpoint) 1.1B Oct 2023 1.9 GB 131k tokens ? Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

EXAONE 4.0 (1.2B) 1.2B Jul 2025 2.0 GB 131k tokens ? Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

LFM2-1.2B 1.2B Jul 2025 2.0 GB 131k tokens ? Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

MinerU2.5 1.2B Sep 2025 2.0 GB 131k tokens ? Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

Pleias 1.0 1.2B 1.2B Dec 2024 2.0 GB 131k tokens ? Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

Pleias-RAG-1B 1.2B Apr 2025 2.0 GB 131k tokens ? Q8_0 Comfortable
734 tok/s

440–1,175 · low confidence

Llama 3.2 1B 1.2B Sep 2024 2.2 GB 131k tokens Q8_0 Comfortable
724 tok/s

434–1,158 · low confidence

MiniCPM-1.2B 1.2B Jun 2024 2.0 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

DeepSeek Coder 1.3B 1.3B Jan 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

DeepSeek-VL-1.3B 1.3B Mar 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

DigiRL 1.3B Jun 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

GLA Transformer 1.3B 1.3B Aug 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

Janus 1.3B 1.3B Oct 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

Kosmos-2.5 1.3B Aug 2024 2.1 GB 131k tokens ? Q8_0 Comfortable
695 tok/s

417–1,111 · low confidence

Otter 1.3B May 2023 2.1 GB 131k tokens ? 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

Data Center GPU Max 1550 full specification

Everything on record for this board, ordered by how much it bears on running a language model rather than by how a spec sheet would list it. Memory comes first because it decides the outcome; the rest is context.

Memory

The two specifications that decide what this card can run and how quickly. Capacity sets which models fit; bandwidth sets how many tokens per second they produce once they do.

Memory size
128 GB
Memory bandwidth
3,280 GB/s
Memory type
HBM2e
Memory bus width
8,192 bit
Memory clock
1.6 GHz

The chip

Which processor is on the board and how it was manufactured. A smaller process size generally means more performance for the same power.

Graphics processor
Ponte Vecchio
Architecture
Generation 12.5
Generation
Data Center GPU(Ponte Vecchio)
Foundry
Intel
Process size
10 nm
Transistors
100 billion
Transistor density
78,100 K/mm²
Die size
1,280 mm²
Released
10 January 2023

Clock speeds

How fast the processor runs. Worth far less here than on a gaming benchmark: generating text is limited by memory bandwidth, so a higher clock barely moves the result.

Base clock
900 MHz
Boost clock
1.6 GHz

Processing units

What the chip contains. These drive graphics performance and matter mainly for processing a long prompt rather than for producing the answer.

Shading units
16,384
Texture mapping units
1,024
Ray tracing cores
128
L1 cache
64 KB
L2 cache
408 MB

Theoretical performance

Peak arithmetic rates published for the board. These are ceilings that no real workload reaches, and generating text reaches a small fraction of them because it is limited by memory rather than arithmetic.

Half precision (FP16)
52.4 TFLOPS
Single precision (FP32)
52.4 TFLOPS
Double precision (FP64)
52.4 TFLOPS
Texture rate
1,638 GTexel/s

The board

What it takes to physically install and power the card — the practical constraints that decide whether it fits the machine you already own.

Power draw (TDP)
600 W
Suggested power supply
1,000 W
Bus interface
PCIe 5.0 x16
Slot width
OAM Module

Software support

Which graphics and compute interfaces the card supports. CUDA compute capability is the one that bears on inference: below 7.0 there are no tensor cores, and modern inference software falls back to slower code paths.

DirectX
12.1
OpenGL
4.6
OpenCL
3.0
Shader model
6.6

Listings

Where to buy a Data Center GPU Max 1550

No vendor is currently listing this card. Listings come from vendors who publish them here directly — browse the vendor directory to see who is selling what.

What the numbers mean

Why memory is the number that matters here

Memory

128 GB

Bandwidth

3,280 GB/s

Largest model

Solar Open2 250B

Data Center GPU Max 1550 holds 128 GB of HBM2e. That puts it in the class of hardware that holds the largest open-weight models without splitting them across machines. An inference runtime can reach roughly 115.2 GB.

Memory bandwidth reaches 3,280 GB/s across a bus of 8,192 bits. That is at the top of what exists. Since each token means reading the whole model out of memory once, it translates almost directly into generation speed — this card is bandwidth-rich enough that model size stops being the limiting factor long before the bus does.

That comes from a memory clock of 1.6 GHz. Both halves matter, and neither is visible in a gaming benchmark.

The practical ceiling is Solar Open2 250B, 250.3B, compressed to Q3_K_M and generating around 54.1 tokens per second.

The chip and how it was built

Data Center GPU Max 1550 is built on the graphics processor Ponte Vecchio, using the architecture Generation 12.5 from Intel, as part of the generation Data Center GPU(Ponte Vecchio).

The chip is manufactured by Intel, on a process of 10 nm, with a die measuring 1,280 mm², holding 100 billion transistors. A smaller process generally means more performance for the same power, though for language models it matters far less than the memory subsystem.

It was released in January 2023, roughly 3.6745632631086 years ago. Inference software support tends to follow hardware by a year or two, so a card of this age generally has mature, well-optimised code paths available to it.

Compute throughput, and why it matters less than it looks

FP16

52.4 TFLOPS

FP64

52.4 TFLOPS

On paper Data Center GPU Max 1550 reaches 52.4 TFLOPS at half precision, and 52.4 TFLOPS at single precision. These are peak figures no real workload sustains, and generating text reaches only a small fraction of them — decoding is limited by memory rather than arithmetic, which is why a card can look enormously powerful here and still produce tokens at an ordinary rate.

Double-precision throughput reaches 52.4 TFLOPS. It has no bearing on running a language model — no inference runtime uses it — but it separates datacentre parts from consumer ones, since the latter deliberately restrict it.

Clocks run from a base of 900 MHz to a boost of 1.6 GHz. Worth far less here than on a gaming benchmark: raising the clock speeds up the arithmetic, and the arithmetic is not what generation is waiting on.

Cache and processing units

Data Center GPU Max 1550 has an L1 cache of 64 KB, backed by an L2 cache of 408 MB. Cache absorbs a share of the memory traffic that would otherwise hit the main bus, which is the one place on this page where a number other than bandwidth quietly affects generation speed — a large L2 lets more of the working set stay close to the cores.

There are 16,384 shading units, 1,024 texture mapping units. These drive graphics workloads and contribute to prompt processing, but they sit idle for much of the time a model spends generating a reply.

Power, size and installation

Power draw

600 W

Data Center GPU Max 1550 is rated at 600 W, and the suggested system power supply is 1,000 W. Running a language model keeps a card busy in bursts rather than continuously — it draws hard while generating and idles between requests — so sustained draw over a working day is usually well below the rated figure.

The board occupies oam module. Worth checking against the case and power supply already in the machine, since the largest cards need considerably more of both than a typical desktop provides.

It connects over PCIe 5.0 x16. The interface governs how quickly a model is loaded from disk into the card, not how fast it runs once there, so a narrower link costs a few seconds at startup and nothing thereafter.

The extremes

The largest AI models that run on a Data Center GPU Max 1550

The biggest open-weight models that fit on this card, newest first. Each is shown at the best compression the card can hold.

  1. 01 Solar Open2 250B 250.3B · Q3_K_M · Jun 2026 54.1 tok/s
  2. 02 MiniMax-M2.7 229B · Q3_K_M · Mar 2026 10.6 tok/s
  3. 03 MiniMax-M2.5 229B · Q3_K_M · Feb 2026 10.6 tok/s
  4. 04 MiniMax-M2.1 229B · Q3_K_M · Dec 2025 10.6 tok/s
  5. 05 P1-235B-A22B 235B · Q3_K_M · Nov 2025 57.6 tok/s
  6. 06 Qwen3-235B-A22B-Thinking (Jul 2025) 235B · Q3_K_M · Jul 2025 57.6 tok/s
  7. 07 Qwen3-235B-A22B (Jul 2025) 235B · Q3_K_M · Jul 2025 57.6 tok/s
  8. 08 Qwen3-235B-A22B 235B · IQ4_XS · Apr 2025 52.4 tok/s
  9. 09 DeepSeek-V2.5 236B · Q3_K_M · Sep 2024 57.4 tok/s
  10. 10 DeepSeek-V2 (MoE-236B) 236B · Q3_K_M · May 2024 57.4 tok/s

The fastest AI models on a Data Center GPU Max 1550

Where this card produces tokens quickest. Smaller models dominate here, because generating each token means reading the whole model out of memory once.

  1. 01 Gemma 3 QAT 1B 1B · Q8_0 · 1.8 GB 903 tok/s
  2. 02 Gemma 3 1B 1B · Q8_0 · 1.8 GB 903 tok/s
  3. 03 LLama 3..2 Typhoon 2 1B 1B · Q8_0 · 1.8 GB 903 tok/s
  4. 04 OLMo-1B 1B · Q8_0 · 1.8 GB 903 tok/s
  5. 05 HGRN 1B (WT 103) 1B · Q8_0 · 1.8 GB 903 tok/s
  6. 06 Pythia-1b 1B · Q8_0 · 1.8 GB 903 tok/s
  7. 07 OpenELM-1.1B 1.1B · Q8_0 · 1.9 GB 836 tok/s
  8. 08 TinyLlama-1.1B (1T token checkpoint) 1.1B · Q8_0 · 1.9 GB 821 tok/s
  9. 09 TinyLlama-1.1B (3T token checkpoint) 1.1B · Q8_0 · 1.9 GB 821 tok/s
  10. 10 DeciCoder-1B 1.1B · Q8_0 · 1.9 GB 821 tok/s

Step by step

How to work out the tokens per second of a Data Center GPU Max 1550

You do not have to calculate anything by hand — the gputps.com calculator on this page has already worked it out for every model this card can hold. Reading off the answer takes six steps.

  1. 01

    Find the model in the table

    The table lists 658 models this card runs. Search narrows the list by name or by size.

  2. 02

    Decide how long your conversations run

    Set the context to your real working length. Short questions cost almost nothing, but a long document can consume a large share of 128 GB that is frequently the difference between a model fitting and not.

  3. 03

    Set a minimum quality if you need one

    Each model is shown at the best compression this card can hold. A minimum quality hides the ones that only fit by being squeezed further than you would accept.

  4. 04

    Look at the range, not just the number

    Each speed is an estimate for a single conversation, with a range beneath it. The top end here is 903 tok/s on Gemma 3 QAT 1B. The same card and model vary by thirty to fifty per cent between inference runtimes.

  5. 05

    Check the headroom before you decide

    The fit column separates models that just fit from those with room to spare — worth checking before settling on one, against an available 128 GB.

  6. 06

    Cross-check against other hardware

    Following a model through to its own page lists all the hardware that can run it, so you can see how it compares against Data Center GPU Max 1550.

Answers

Data Center GPU Max 1550 — common questions

01

Data Center GPU Max 1550— can it run 7B models?

Yes. For example it runs Gemma 4 E4B at Q8_0, using about 9.8 GB of memory and generating around 201 tokens per second.

02

Data Center GPU Max 1550— can it run 13B models?

Yes. For example it runs DeepSeekMoE-16B at Q8_0, using about 17.5 GB of memory and generating around 314 tokens per second.

03

Data Center GPU Max 1550— can it run 30B models?

Yes. For example it runs ERNIE-4.5-VL-28B-A3B at Q8_0, using about 29.2 GB of memory and generating around 179 tokens per second.

04

Data Center GPU Max 1550— can it run 70B models?

Yes. For example it runs Qwen3-Coder-Next at Q8_0, using about 80.7 GB of memory and generating around 62.7 tokens per second.

05

Data Center GPU Max 1550— how much memory does it have?

This card has 128 GB of HBM2e. Around a tenth is reserved by the inference runtime and the driver, leaving roughly 115.2 GB available for a model and its conversation.

06

Data Center GPU Max 1550— what is its memory bandwidth?

Memory bandwidth reaches 3,280 GB/s across a bus of 8,192 bits. This is the single best predictor of how fast it generates text, because producing each token means reading the entire model out of memory once.

07

Data Center GPU Max 1550— what type of memory does it use?

It uses HBM2e clocked at 1.6 GHz. HBM types are found on datacentre accelerators and carry far more bandwidth than the GDDR used on desktop cards, which is why they generate tokens considerably faster at the same capacity.

08

Data Center GPU Max 1550— who makes it?

This is a product of Intel, with the chip manufactured by Intel, on a process of 10 nm.

09

Data Center GPU Max 1550— when was it released?

It was released in January 2023.

10

Data Center GPU Max 1550— how much power does it use?

Rated board power is 600 W, and the suggested system power supply is 1,000 W. Generating text draws hard in bursts and idles between requests, so average consumption over a working session is normally well below the rated figure.

11

Data Center GPU Max 1550— how much cache does it have?

The L1 cache is 64 KB, and the L2 cache is 408 MB. Cache absorbs part of the memory traffic that would otherwise reach the main bus, so a larger L2 gives a modest lift to generation speed beyond what bandwidth alone predicts.

12

Data Center GPU Max 1550— what are its TFLOPS?

It is rated at 52.4 TFLOPS at half precision and 52.4 TFLOPS at single precision. These are peak arithmetic ceilings rather than achievable rates, and text generation reaches only a small fraction of them because it is limited by memory bandwidth instead.

13

Data Center GPU Max 1550— does it support CUDA?

No. CUDA is NVIDIA-only, and this is a card from Intel. It runs language models through ROCm, Vulkan or Metal depending on the software, which are less mature than the CUDA path — our estimates apply a penalty for that.

14

Data Center GPU Max 1550— what bus interface does it use?

It uses PCIe 5.0 x16. This governs how fast a model is loaded onto the card rather than how fast it runs once loaded, so it costs a few seconds at startup and nothing during generation.

15

Data Center GPU Max 1550— is it good for running local AI models?

Its memory is large enough for models most desktop hardware cannot touch and its bandwidth puts it among the fastest hardware available for generation. In total it runs 658 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.

16

Data Center GPU Max 1550— can it run a model that does not fit in its memory?

Only partly. Layers beyond the card's 128 GB is possible and usually a false economy: the system-memory portion is slow enough to dominate the result.

17

Would two Data Center GPU Max 1550 cards be twice as fast?

Pairing them buys headroom rather than pace: 256 GB of combined memory, at roughly the same generation speed as one.

18

Data Center GPU Max 1550— which AI models can it run?

658 of the 721 open-weight language models we track fit on this card and can be run locally. The table on this page lists every one, with the memory it needs, the quantisation it runs at and an estimated generation speed.

19

Data Center GPU Max 1550— what is the largest AI model it can run?

The largest model in our catalogue that fits is Solar Open2 250B at 250.3B parameters, compressed to Q3_K_M. It generates roughly 54.1 tokens per second and needs about 106.6 GB of the card's memory.

20

Data Center GPU Max 1550— how many tokens per second does it produce?

It depends on the model. The fastest model we track here is Gemma 3 QAT 1B at about 903 tokens per second, while larger models run proportionally slower because each token requires reading the whole model out of memory once. Speeds are estimates for a single conversation at a time.

The other direction

Looking at it from the other side?

This page starts from the hardware. If you already know which model you want and need to know what it takes to run it, start from the model instead.

All GPUs