Can the NVIDIA RTX PRO 6000 Blackwell Workstation Edition run MiniMax-M2.7?

MiniMax-M2.7 · NVIDIA RTX PRO 6000 Blackwell Workstation Edition · 8,192 ctx · whole model residentQ2_K sizereconstructed sizeSpeedestimate

IT FITS

Yes. 1 of 9 formats evaluated fit in 96 GB, at 8,192 tokens. No published file exists for this pair, so every size is rebuilt from the pinned architecture. The best quality that fits is Q2_K, needing 86.0 GB and running at an estimated 195 tokens per second.

Fitting in memory is not the same as loading. Whether the runtime and version you have supports this architecture and format on this machine has not been tested here.

Find the NVIDIA RTX PRO 6000 Blackwell Workstation Edition: Amazon ↗ · eBay (new and used) ↗Store links may pay us a commission. They never decide which card is suggested — the memory arithmetic does.

1/9formats that fit

96 GBdevice memory

86.0 GBneeded at best quality

~195tokens per second, estimatedFaster than you read

1792GB/s bandwidth

Run it in the cloud

Run MiniMax-M2.7 properly, for cents an hour

The NVIDIA RTX PRO 6000 Blackwell Workstation Edition only holds it at Q2_K, at an estimated ~195 tokens per second. A rented card runs a better format at full speed, billed by the second.

Your card Or keep Q4_K_M on your own card: with about 47 GB of it in system RAM, the NVIDIA RTX PRO 6000 Blackwell Workstation Edition runs it at ~24 tokens per second (about reading pace) — free, if you have the RAM. A rented card below holds all of it on the GPU. Size the offload →

Prices · 18:30 UTC, 22 Sept

Cheapest192 GB

4× L40S

$1.87per hour

Speed: ~273 tok/sFaster than you read
Per million tokens: $1.90

Vast.ai · Marketplace · 99.2% reliable

Rent on Vast.ai

Lowest price per hour

Recommended192 GB

8× RTX 4090

$4.06per hour

Speed: ~638 tok/sFaster than you read
Per million tokens: $1.77

Vast.ai · Marketplace · 99.2% reliable

Rent on Vast.ai

Lowest cost per token at 20+ tok/s

Fastest282 GB

2× H200

$9.18per hour

Speed: ~759 tok/sFaster than you read
Per million tokens: $3.36

RunPod · Secure Cloud

Rent on RunPod

or Vast.ai $10.00/h

Compare all 10 rentable configurations →

No GPU at all

Use MiniMax-M2.7 by the token

Novita AI$1.20 / M output · $0.30 / M inputOpen on Novita AI
OpenRouter$1.20 / M output · $0.30 / M inputOpen on OpenRouter

For one person chatting, that is about 1.5× cheaper than the best-value rented card above ($1.77 per million tokens). A rented GPU pays off when you keep it busy — many requests batched together, long agent runs — or when the data must stay on a machine you control, or the exact file you want is not served anywhere.

First time renting a GPU? How it works, in four steps

Create an account and add credit. Both providers are prepaid: $10 is enough to try any card on this page for hours. A new RunPod account that arrives through a referral link gets a one-time $5 credit when it first adds $10.
Pick the card and the count shown here, and a template: llama.cpp or vLLM for an OpenAI-compatible API, or one with a web chat if you only want to talk to the model. “How to launch it” below gives the exact image and command.
Wait for the download. The weights are fetched on the machine; tens of gigabytes take a few minutes on a data-centre connection. You pay by the second from the moment it starts.
Stop it when you are done. A running machine bills even when idle. A stopped one costs nothing per hour, though its disk is usually still billed until you delete it.

How to launch it

No Q4_K_M file of MiniMax-M2.7 is catalogued here, so there is no exact command to vouch for. Start the machine from the llama.cpp server image ghcr.io/ggml-org/llama.cpp:server-cuda and point -hf at a Q4_K_M build from the publisher or a quantizer you trust — search Hugging Face for one. Check its file size against the memory figure on this page before you rent.

Every machine holds the whole model at Q4_K_M and 8,192 tokens of context, no offload. Speeds are this site’s single-stream decode estimates; prices are what each provider’s own API quoted, on-demand, for the whole machine. Vast hosts below 98% measured reliability are left out.

Referral links Vast.ai, RunPod and Novita pay us a share of what you spend if you sign up through these buttons. It costs you nothing, and it never decides an order or a recommendation: both are computed from the live price and the speed, and options that pay us nothing are listed and recommended on the same terms. How we rank

Runs well on your NVIDIA RTX PRO 6000 Blackwell Workstation Edition instead

The models nearest to MiniMax-M2.7 — same lab first, then closest in size — that the NVIDIA RTX PRO 6000 Blackwell Workstation Edition holds whole at the standard format and runs at a usable speed. Nearest in size is not the same as equally good; compare them on the task you care about.

Ling-3.0-flashQ4_K_M · 78.2 GB · ~398 tok/s
NVIDIA-Nemotron-3-Super-120B-A12B-BF16Q4_K_M · 76.9 GB · ~16 tok/s
Qwen3.5-122B-A10BQ4_K_M · 77.9 GB · ~241 tok/s
Devstral-2-123B-Instruct-2512Q4_K_M · 78.6 GB · ~16 tok/s

How long a conversation. At Q2_K, this pair holds 47,426 tokens of context — roughly 35,570 words — needing 96.0 GB. Past that the NVIDIA RTX PRO 6000 Blackwell Workstation Edition runs out of memory, not the model out of context, which would allow 204,800. This is the wall a long chat hits after it has already loaded fine. The nearest round setting below it is 32,768.

Every format evaluated

No published file exists for this pair, so every size is rebuilt from the pinned architecture. The Basis column says which is which for each row. Decode and first-token figures are calibrated estimates, not runs on this card.

Format	Needs	Of 96 GB	Fits	Decode	First token	Basis
FP16	460.4 GB	480%	short by 364.4 GB	does not run	—	reconstructed size
Q8_0	246.0 GB	256%	short by 150.0 GB	does not run	—	reconstructed size
Q6_K	190.6 GB	199%	short by 94.6 GB	does not run	—	reconstructed size
Q5_K_M	165.2 GB	172%	short by 69.2 GB	does not run	—	reconstructed size
Q5_0	160.4 GB	167%	short by 64.4 GB	does not run	—	reconstructed size
Q4_K_M	141.2 GB	147%	short by 45.2 GB	does not run	—	reconstructed size
Q4_0	131.9 GB	137%	short by 35.9 GB	does not run	—	reconstructed size
Q3_K_M	116.1 GB	121%	short by 20.1 GB	does not run	—	reconstructed size
Q2_K	86.0 GB	90%	yes	~195 tok/s	no comparable peak	reconstructed size

Sized at 8,192 tokens of context with the whole model resident — weights, the KV cache and the runtime reserve, offload off. Speed is only quoted for a format that fits: a rate for a configuration that cannot load is not a fact about anything.

Why the first-token figure is the same on every row

First token is modelled from the arithmetic the prompt requires, and that count does not change with the weight format — which is why it reads the same on every row. Real prefill does vary by format, because a quantized matmul is a different kernel; this model does not capture that, and the figure should be read as an order of magnitude rather than a ranking between formats.

What the labels mean

published data: Read from a published source — a file's byte count, a model's configuration or a manufacturer's specification — or exact arithmetic on such values. Not a measurement on a machine.
reconstructed size: Weight size reconstructed from the pinned architecture, because no published file exists.
size range: Only a lower and an upper bound are claimed for this weight size.
estimate: Calculated from sourced inputs by a stated method; an estimate, not a measurement.

Change anything

This page fixes the context at 8,192 tokens and one device. Batch, concurrent users, KV-cache format, clusters and rental cost are all in the calculator, already set to this pairing.

Open in the calculator →Everything the NVIDIA RTX PRO 6000 Blackwell Workstation Edition runs Best models for 96 GB

Where these numbers come from

MiniMax-M2.7’s architecture is read from its publisher’s own config.json at a pinned revision, and the NVIDIA RTX PRO 6000 Blackwell Workstation Edition’s 96 GB and 1792 GB/s come from the manufacturer’s specification. How far each figure can be trusted is published, per format and worst case included, on the accuracy scorecard.

Building this into your own product? A free API key returns exactly these figures, and the widget puts this answer on a product page with one script tag.

Use this answer in your own product

As JSON, from the API

curl -s https://llmbottleneck.com/v1/analyze \
  -H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
  -d '{"model":"minimaxai-minimax-m2-7","quantization":"Q2_K","context":8192,"hardware":"nvidia-rtx-pro-6000-blackwell-workstation"}'

Same engine, same evidence, every field sourced. Free key in one step →

On your page, as a widget

<script src="https://llmbottleneck.com/widget.js"
  data-model="minimaxai-minimax-m2-7" data-quantization="Q2_K"
  data-hardware="nvidia-rtx-pro-6000-blackwell-workstation" data-context="8192"></script>

No key needed. Unbranded, with your own buy button, on Pro and Business →