RunInfraby RightNow
  • CatalogNew
  • Pricing
  • Research
  • Contact
DashboardSign inGet started

See what this model actually costs to serve.

Fit is always evaluated when model sizing is available. GPU rent, paid idle capacity, API crossover, and measured optimization appear only when their required evidence exists. When the API wins, the page says so.

Mixtral-8x7B-Instruct-v0.1 does not fit on 1 x NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB: 108.7 GB required, 86.4 GB available.

Fit is always evaluated when model sizing is available. GPU rent, paid idle capacity, API crossover, and measured optimization appear only when their required evidence exists. When the API wins, the page says so.

Model

mistralai/Mixtral-8x7B-Instruct-v0.1

GPU

NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB

Requests/day

50,000

GPU count

1

Quantization

FP16

Tokens/request

500 in, 500 out

Charts appear only when evidence existsUtilization defaults to 30%

Configure the workload

Change the inputs, then calculate a shareable result.

Hugging Face model

Utilization assumption

Defaulted to 30% so the page does not manufacture a self-hosting win.

Derived utilization

Needs throughput

Idle share paid

Needs throughput

Utilization assumption30%

A steady production service with real peaks and troughs.

At this level about 70% of every rented GPU hour sits idle, and it is billed at the same rate as a busy one.

Does not fit

This configuration needs more memory.

The model and KV cache need more VRAM than the selected GPU count provides. Cost is intentionally hidden for a configuration that cannot run.

Model

mistralai/Mixtral-8x7B-Instruct-v0.1

Hardware

1 x NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB, FP16

Memory fit

Weights and KV cache stay separate so the fit is reproducible.

93.4 GB
Model weights
1.1 GB
KV cache
108.7 GB
Total required
86.4 GB
Available
8,192 tokens
Served context used
14.2 GB
Runtime overhead
Exact transformer shape
KV cache method

Memory-fit rental floors

Published rent floors for memory-fitting configurations.

Each row uses an engine GPU fit when present; the remaining catalog GPUs apply this result's required memory to published VRAM. GPU count rises only enough to clear memory.

Engine memory-fit result

Memory fit: 4x NVIDIA GeForce RTX 5090 32 GB at 90% vLLM GPU memory utilization.

On-demand rates are preferred for each GPU; when none is captured, the lowest dated captured tier is used. The rentable GPU catalog is ranked by one-deployment monthly rent over the contract's 730.5-hour month, rounded to cents. Equal displayed prices share a rank. These are arithmetic floors, not provider offers. Throughput, replica demand, traffic capacity, topology support, and current availability are not established.

  1. Floor rank 1

    6 x NVIDIA RTX A5000 24 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $701.28

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 6 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  2. Floor rank 2

    3 x NVIDIA RTX A6000 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $723.20

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  3. Floor rank 3

    3 x NVIDIA A40 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 696 GB/s memory bandwidth

    One-deployment monthly rent floor

    $767.03

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source

What to change

Computed actions and cost signals appear only when the result supports them.

RecommendationComputed memory fit

Consider FP8 or INT8 if the checkpoint and hardware support it

FP16 weights use 93.4 GB and bring total memory to 108.7 GB; FP8 or INT8 would lower weights to 46.7 GB and total memory to 47.8 GB, which fits inside 86.4 GB.

Show 1 more computed option
RecommendationComputed memory fit

Raise tensor parallel size to 2

The current vLLM command uses tensor parallel size 1 and provides 86.4 GB, while 108.7 GB requires 2 same-GPU workers for 172.8 GB; raise --tensor-parallel-size to 2 if the model topology supports it.

Decode bandwidth ceiling

A physics bound, not an expected throughput result.

17 output tok/sCeiling

Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.

Decode ceiling derived from GPU memory bandwidth and model weight bytes, as of 2026-08-08

Reproduce with vLLM

The exact command attached to this result.

vllm serve 'mistralai/Mixtral-8x7B-Instruct-v0.1' --dtype float16 --tensor-parallel-size 1 --max-model-len 8192 --gpu-memory-utilization 0.9

Sources and caveats

Every published number keeps its source and date.

Provenance

  • Hugging Face model API revision sha

    As of 2026-08-08

  • Hugging Face model API safetensors.total

    As of 2026-08-08

  • config.json:max_position_embeddings

    As of 2026-08-08

  • config.json:architectures[0]

    As of 2026-08-08

  • NVIDIA RTX PRO AI Factory, RTX PRO 6000 Blackwell Server Edition specifications

    As of 2026-08-08

  • Hugging Face config.json transformer shape

    As of 2026-08-08

  • RunInfra Engine feasibility runtime-overhead policy

    As of 2026-08-09

  • Decode ceiling derived from GPU memory bandwidth and model weight bytes

    As of 2026-08-08

  • vLLM serve CLI documentation

    As of 2026-08-08

  • NVIDIA H200 Tensor Core GPU datasheet

    As of 2026-08-08

  • NVIDIA Blackwell architecture specification

    As of 2026-08-08

  • NVIDIA Blackwell Ultra Datasheet, page 5, HGX B300 individual-GPU sparse specifications; footnote 2: 'Specification in sparse. Dense is ½ sparse spec shown.' Dense fp16 is 4.5 / 2 = 2.25 PFLOPS and dense fp8 is 9 / 2 = 4.5 PFLOPS

    As of 2026-08-09

  • AMD Instinct MI300X data sheet

    As of 2026-08-08

Caveats

  • +Served context is 8192 tokens. It is a serving-capacity decision and is not inferred from average input or output tokens.
  • +KV cache uses the exact transformer-shape formula with 32 layers, 8 KV heads, and head dimension 128.
  • +Runtime overhead adds 14.17 GB to totalRequiredGb. This approximate 15% policy allowance covers CUDA context, activations, and vLLM overhead. Deployment-time profiling, including CUDA graph capture and allocator behavior, can differ.
  • +Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.
  • +No dense compute ceiling is cited for fp16 on NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB. The available physics bound is decode-only, so the entry point returns no cost instead of copying decode throughput into the input field.
  • +CalcInput has no GPU provider selector. The calculation uses the lowest supplied on-demand rate for RTX-PRO-6000-Blackwell-Server: Hyperstack at $1.85/GPU-hour.
  • +The selected configuration does not fit, so no cost is returned.

Does not fit

This configuration needs more memory.

The model and KV cache need more VRAM than the selected GPU count provides. Cost is intentionally hidden for a configuration that cannot run.

Model

mistralai/Mixtral-8x7B-Instruct-v0.1

Hardware

1 x NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB, FP16

Memory fit

Weights and KV cache stay separate so the fit is reproducible.

93.4 GB
Model weights
1.1 GB
KV cache
108.7 GB
Total required
86.4 GB
Available
8,192 tokens
Served context used
14.2 GB
Runtime overhead
Exact transformer shape
KV cache method

Memory-fit rental floors

Published rent floors for memory-fitting configurations.

Each row uses an engine GPU fit when present; the remaining catalog GPUs apply this result's required memory to published VRAM. GPU count rises only enough to clear memory.

Engine memory-fit result

Memory fit: 4x NVIDIA GeForce RTX 5090 32 GB at 90% vLLM GPU memory utilization.

On-demand rates are preferred for each GPU; when none is captured, the lowest dated captured tier is used. The rentable GPU catalog is ranked by one-deployment monthly rent over the contract's 730.5-hour month, rounded to cents. Equal displayed prices share a rank. These are arithmetic floors, not provider offers. Throughput, replica demand, traffic capacity, topology support, and current availability are not established.

  1. Floor rank 1

    6 x NVIDIA RTX A5000 24 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $701.28

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 6 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  2. Floor rank 2

    3 x NVIDIA RTX A6000 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $723.20

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  3. Floor rank 3

    3 x NVIDIA A40 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 696 GB/s memory bandwidth

    One-deployment monthly rent floor

    $767.03

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source

What to change

Computed actions and cost signals appear only when the result supports them.

RecommendationComputed memory fit

Consider FP8 or INT8 if the checkpoint and hardware support it

FP16 weights use 93.4 GB and bring total memory to 108.7 GB; FP8 or INT8 would lower weights to 46.7 GB and total memory to 47.8 GB, which fits inside 86.4 GB.

Show 1 more computed option
RecommendationComputed memory fit

Raise tensor parallel size to 2

The current vLLM command uses tensor parallel size 1 and provides 86.4 GB, while 108.7 GB requires 2 same-GPU workers for 172.8 GB; raise --tensor-parallel-size to 2 if the model topology supports it.

Decode bandwidth ceiling

A physics bound, not an expected throughput result.

17 output tok/sCeiling

Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.

Decode ceiling derived from GPU memory bandwidth and model weight bytes, as of 2026-08-08

Reproduce with vLLM

The exact command attached to this result.

vllm serve 'mistralai/Mixtral-8x7B-Instruct-v0.1' --dtype float16 --tensor-parallel-size 1 --max-model-len 8192 --gpu-memory-utilization 0.9

Sources and caveats

Every published number keeps its source and date.

Provenance

  • Hugging Face model API revision sha

    As of 2026-08-08

  • Hugging Face model API safetensors.total

    As of 2026-08-08

  • config.json:max_position_embeddings

    As of 2026-08-08

  • config.json:architectures[0]

    As of 2026-08-08

  • NVIDIA RTX PRO AI Factory, RTX PRO 6000 Blackwell Server Edition specifications

    As of 2026-08-08

  • Hugging Face config.json transformer shape

    As of 2026-08-08

  • RunInfra Engine feasibility runtime-overhead policy

    As of 2026-08-09

  • Decode ceiling derived from GPU memory bandwidth and model weight bytes

    As of 2026-08-08

  • vLLM serve CLI documentation

    As of 2026-08-08

  • NVIDIA H200 Tensor Core GPU datasheet

    As of 2026-08-08

  • NVIDIA Blackwell architecture specification

    As of 2026-08-08

  • NVIDIA Blackwell Ultra Datasheet, page 5, HGX B300 individual-GPU sparse specifications; footnote 2: 'Specification in sparse. Dense is ½ sparse spec shown.' Dense fp16 is 4.5 / 2 = 2.25 PFLOPS and dense fp8 is 9 / 2 = 4.5 PFLOPS

    As of 2026-08-09

  • AMD Instinct MI300X data sheet

    As of 2026-08-08

Caveats

  • +Served context is 8192 tokens. It is a serving-capacity decision and is not inferred from average input or output tokens.
  • +KV cache uses the exact transformer-shape formula with 32 layers, 8 KV heads, and head dimension 128.
  • +Runtime overhead adds 14.17 GB to totalRequiredGb. This approximate 15% policy allowance covers CUDA context, activations, and vLLM overhead. Deployment-time profiling, including CUDA graph capture and allocator behavior, can differ.
  • +Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.
  • +No dense compute ceiling is cited for fp16 on NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB. The available physics bound is decode-only, so the entry point returns no cost instead of copying decode throughput into the input field.
  • +CalcInput has no GPU provider selector. The calculation uses the lowest supplied on-demand rate for RTX-PRO-6000-Blackwell-Server: Hyperstack at $1.85/GPU-hour.
  • +The selected configuration does not fit, so no cost is returned.

Does not fit

This configuration needs more memory.

The model and KV cache need more VRAM than the selected GPU count provides. Cost is intentionally hidden for a configuration that cannot run.

Model

mistralai/Mixtral-8x7B-Instruct-v0.1

Hardware

1 x NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB, FP16

Memory fit

Weights and KV cache stay separate so the fit is reproducible.

93.4 GB
Model weights
1.1 GB
KV cache
108.7 GB
Total required
86.4 GB
Available
8,192 tokens
Served context used
14.2 GB
Runtime overhead
Exact transformer shape
KV cache method

Memory-fit rental floors

Published rent floors for memory-fitting configurations.

Each row uses an engine GPU fit when present; the remaining catalog GPUs apply this result's required memory to published VRAM. GPU count rises only enough to clear memory.

Engine memory-fit result

Memory fit: 4x NVIDIA GeForce RTX 5090 32 GB at 90% vLLM GPU memory utilization.

On-demand rates are preferred for each GPU; when none is captured, the lowest dated captured tier is used. The rentable GPU catalog is ranked by one-deployment monthly rent over the contract's 730.5-hour month, rounded to cents. Equal displayed prices share a rank. These are arithmetic floors, not provider offers. Throughput, replica demand, traffic capacity, topology support, and current availability are not established.

  1. Floor rank 1

    6 x NVIDIA RTX A5000 24 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $701.28

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 6 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  2. Floor rank 2

    3 x NVIDIA RTX A6000 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $723.20

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  3. Floor rank 3

    3 x NVIDIA A40 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 696 GB/s memory bandwidth

    One-deployment monthly rent floor

    $767.03

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source

What to change

Computed actions and cost signals appear only when the result supports them.

RecommendationComputed memory fit

Consider FP8 or INT8 if the checkpoint and hardware support it

FP16 weights use 93.4 GB and bring total memory to 108.7 GB; FP8 or INT8 would lower weights to 46.7 GB and total memory to 47.8 GB, which fits inside 86.4 GB.

Show 1 more computed option
RecommendationComputed memory fit

Raise tensor parallel size to 2

The current vLLM command uses tensor parallel size 1 and provides 86.4 GB, while 108.7 GB requires 2 same-GPU workers for 172.8 GB; raise --tensor-parallel-size to 2 if the model topology supports it.

Decode bandwidth ceiling

A physics bound, not an expected throughput result.

17 output tok/sCeiling

Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.

Decode ceiling derived from GPU memory bandwidth and model weight bytes, as of 2026-08-08

Reproduce with vLLM

The exact command attached to this result.

vllm serve 'mistralai/Mixtral-8x7B-Instruct-v0.1' --dtype float16 --tensor-parallel-size 1 --max-model-len 8192 --gpu-memory-utilization 0.9

Sources and caveats

Every published number keeps its source and date.

Provenance

  • Hugging Face model API revision sha

    As of 2026-08-08

  • Hugging Face model API safetensors.total

    As of 2026-08-08

  • config.json:max_position_embeddings

    As of 2026-08-08

  • config.json:architectures[0]

    As of 2026-08-08

  • NVIDIA RTX PRO AI Factory, RTX PRO 6000 Blackwell Server Edition specifications

    As of 2026-08-08

  • Hugging Face config.json transformer shape

    As of 2026-08-08

  • RunInfra Engine feasibility runtime-overhead policy

    As of 2026-08-09

  • Decode ceiling derived from GPU memory bandwidth and model weight bytes

    As of 2026-08-08

  • vLLM serve CLI documentation

    As of 2026-08-08

  • NVIDIA H200 Tensor Core GPU datasheet

    As of 2026-08-08

  • NVIDIA Blackwell architecture specification

    As of 2026-08-08

  • NVIDIA Blackwell Ultra Datasheet, page 5, HGX B300 individual-GPU sparse specifications; footnote 2: 'Specification in sparse. Dense is ½ sparse spec shown.' Dense fp16 is 4.5 / 2 = 2.25 PFLOPS and dense fp8 is 9 / 2 = 4.5 PFLOPS

    As of 2026-08-09

  • AMD Instinct MI300X data sheet

    As of 2026-08-08

Caveats

  • +Served context is 8192 tokens. It is a serving-capacity decision and is not inferred from average input or output tokens.
  • +KV cache uses the exact transformer-shape formula with 32 layers, 8 KV heads, and head dimension 128.
  • +Runtime overhead adds 14.17 GB to totalRequiredGb. This approximate 15% policy allowance covers CUDA context, activations, and vLLM overhead. Deployment-time profiling, including CUDA graph capture and allocator behavior, can differ.
  • +Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.
  • +No dense compute ceiling is cited for fp16 on NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB. The available physics bound is decode-only, so the entry point returns no cost instead of copying decode throughput into the input field.
  • +CalcInput has no GPU provider selector. The calculation uses the lowest supplied on-demand rate for RTX-PRO-6000-Blackwell-Server: Hyperstack at $1.85/GPU-hour.
  • +The selected configuration does not fit, so no cost is returned.

Does not fit

This configuration needs more memory.

The model and KV cache need more VRAM than the selected GPU count provides. Cost is intentionally hidden for a configuration that cannot run.

Model

mistralai/Mixtral-8x7B-Instruct-v0.1

Hardware

1 x NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB, FP16

Memory fit

Weights and KV cache stay separate so the fit is reproducible.

93.4 GB
Model weights
1.1 GB
KV cache
108.7 GB
Total required
86.4 GB
Available
8,192 tokens
Served context used
14.2 GB
Runtime overhead
Exact transformer shape
KV cache method

Memory-fit rental floors

Published rent floors for memory-fitting configurations.

Each row uses an engine GPU fit when present; the remaining catalog GPUs apply this result's required memory to published VRAM. GPU count rises only enough to clear memory.

Engine memory-fit result

Memory fit: 4x NVIDIA GeForce RTX 5090 32 GB at 90% vLLM GPU memory utilization.

On-demand rates are preferred for each GPU; when none is captured, the lowest dated captured tier is used. The rentable GPU catalog is ranked by one-deployment monthly rent over the contract's 730.5-hour month, rounded to cents. Equal displayed prices share a rank. These are arithmetic floors, not provider offers. Throughput, replica demand, traffic capacity, topology support, and current availability are not established.

  1. Floor rank 1

    6 x NVIDIA RTX A5000 24 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $701.28

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 6 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  2. Floor rank 2

    3 x NVIDIA RTX A6000 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 768 GB/s memory bandwidth

    One-deployment monthly rent floor

    $723.20

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source
  3. Floor rank 3

    3 x NVIDIA A40 48 GB

    Memory fits

    108.7 GB required, 129.6 GB available inside the engine memory budget.

    Current result memory total, Ampere, 696 GB/s memory bandwidth

    One-deployment monthly rent floor

    $767.03

    RunPod, Community Cloud, on demand

    Captured 2026-08-08

    Arithmetic floor for 3 GPUs over the contract's 730.5-hour month. This is not a provider offer.

    Open rental source

What to change

Computed actions and cost signals appear only when the result supports them.

RecommendationComputed memory fit

Consider FP8 or INT8 if the checkpoint and hardware support it

FP16 weights use 93.4 GB and bring total memory to 108.7 GB; FP8 or INT8 would lower weights to 46.7 GB and total memory to 47.8 GB, which fits inside 86.4 GB.

Show 1 more computed option
RecommendationComputed memory fit

Raise tensor parallel size to 2

The current vLLM command uses tensor parallel size 1 and provides 86.4 GB, while 108.7 GB requires 2 same-GPU workers for 172.8 GB; raise --tensor-parallel-size to 2 if the model topology supports it.

Decode bandwidth ceiling

A physics bound, not an expected throughput result.

17 output tok/sCeiling

Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.

Decode ceiling derived from GPU memory bandwidth and model weight bytes, as of 2026-08-08

Reproduce with vLLM

The exact command attached to this result.

vllm serve 'mistralai/Mixtral-8x7B-Instruct-v0.1' --dtype float16 --tensor-parallel-size 1 --max-model-len 8192 --gpu-memory-utilization 0.9

Sources and caveats

Every published number keeps its source and date.

Provenance

  • Hugging Face model API revision sha

    As of 2026-08-08

  • Hugging Face model API safetensors.total

    As of 2026-08-08

  • config.json:max_position_embeddings

    As of 2026-08-08

  • config.json:architectures[0]

    As of 2026-08-08

  • NVIDIA RTX PRO AI Factory, RTX PRO 6000 Blackwell Server Edition specifications

    As of 2026-08-08

  • Hugging Face config.json transformer shape

    As of 2026-08-08

  • RunInfra Engine feasibility runtime-overhead policy

    As of 2026-08-09

  • Decode ceiling derived from GPU memory bandwidth and model weight bytes

    As of 2026-08-08

  • vLLM serve CLI documentation

    As of 2026-08-08

  • NVIDIA H200 Tensor Core GPU datasheet

    As of 2026-08-08

  • NVIDIA Blackwell architecture specification

    As of 2026-08-08

  • NVIDIA Blackwell Ultra Datasheet, page 5, HGX B300 individual-GPU sparse specifications; footnote 2: 'Specification in sparse. Dense is ½ sparse spec shown.' Dense fp16 is 4.5 / 2 = 2.25 PFLOPS and dense fp8 is 9 / 2 = 4.5 PFLOPS

    As of 2026-08-09

  • AMD Instinct MI300X data sheet

    As of 2026-08-08

Caveats

  • +Served context is 8192 tokens. It is a serving-capacity decision and is not inferred from average input or output tokens.
  • +KV cache uses the exact transformer-shape formula with 32 layers, 8 KV heads, and head dimension 128.
  • +Runtime overhead adds 14.17 GB to totalRequiredGb. This approximate 15% policy allowance covers CUDA context, activations, and vLLM overhead. Deployment-time profiling, including CUDA graph capture and allocator behavior, can differ.
  • +Bandwidth decode CEILING, not expected throughput. Ideal tensor-parallel scaling is assumed. Real decode throughput is lower.
  • +No dense compute ceiling is cited for fp16 on NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB. The available physics bound is decode-only, so the entry point returns no cost instead of copying decode throughput into the input field.
  • +CalcInput has no GPU provider selector. The calculation uses the lowest supplied on-demand rate for RTX-PRO-6000-Blackwell-Server: Hyperstack at $1.85/GPU-hour.
  • +The selected configuration does not fit, so no cost is returned.

Share this calculation

Embed code appears only when the calculator can publish a sourced cost for a fitting configuration.

Badge unavailable for this configuration

This configuration does not fit the selected hardware, so the calculator does not publish a cost or embed code.

Use it from an agent or script

GET the current inputs, or inspect the descriptor for accepted parameters and response fields.

Endpoint
GET https://runinfra.ai/api/calchttps://runinfra.ai/api/calc?hfId=mistralai%2FMixtral-8x7B-Instruct-v0.1&gpuId=RTX-PRO-6000-Blackwell-Server&gpuCount=1&requestsPerDay=50000&avgInputTokens=500&avgOutputTokens=500&utilization=0.3&quantization=fp16
Canonical result
https://runinfra.ai/calc/mixtral-8x7b/rtx-pro-6000-blackwell-server/50k-req-day?context=8192
Descriptor
https://runinfra.ai/api/calc/schema

28 GPU ids, 7 quantizations

Make this configuration fit, describe what you need

Describe how you want to deploy this configuration...
ModelsAuto engineAuto GPU
End-to-end encryption
Isolated GPU infrastructure
No training on your data
SOC 2 Type II
RunInfraby RightNow

© 2026 RunInfra. All rights reserved.

System status
Pipeline BuilderModelsCost CalculatorPricingStartupsBenchmarksDocsResearchNewsContact
Backed by
YCombinator
AICPA Type II
SOC 2
NVIDIA Inception ProgramNVIDIA Inception Program
Ask AI about RunInfra
Part of RightNow
SecurityDPAAUPCookiesTermsPrivacy