Skip to main content

Synopsis

Description

Estimates hardware requirements for running a specific model with a given configuration. This is useful for:
  • Planning hardware upgrades
  • Sizing cloud instances
  • Understanding resource needs before deployment
  • Evaluating different quantization options

Arguments

string
required
Model name or unique partial name to analyze.

Required Options

integer
required
Context length for estimation in tokens. Must be >= 1.

Optional Flags

string
Quantization override (e.g., “Q4_K_M”, “Q8_0”, “mlx-4bit”). If not specified, uses the model’s default quantization.
float
Target decode speed in tokens/second. Shows what hardware is needed to achieve this throughput.
boolean
default:"false"
Output plan as JSON instead of formatted text.
string
Override GPU VRAM size for current system comparison (e.g., “32G”).

Usage Examples

Basic Planning

Custom Quantization

Target Throughput

JSON Output

Compare Configurations

Example Output

Human-Readable Format

With Target TPS

JSON Format

MoE Model Planning

Planning Use Cases

Cloud Instance Sizing

Hardware Upgrade Planning

Development Environment Setup

Estimation Methodology

Memory Calculation

  • Model Weights: params × bytes_per_param (quantization-dependent)
  • KV Cache: context × layers × hidden_dim × 2 (K+V) × bytes_per_element
  • Activations: ~10-15% overhead for intermediate activations
  • OS/Runtime: Additional 2-4GB for system processes

Quantization Impact

Run Paths

  • GPU: Full model on GPU (best performance)
  • MoE Offload: Active experts on GPU, inactive in RAM
  • CPU Offload: Some layers on CPU, rest on GPU
  • CPU Only: Full model on CPU (slowest)
  • info - Detailed model information
  • fit - Check current system compatibility
  • system - View current hardware specs
  • recommend - Get model recommendations