Profiler Guide

This guide covers deployment, configuration, integration, and troubleshooting for the Dynamo Profiler.

What is a DynamoGraphDeploymentRequest (DGDR)?

A DynamoGraphDeploymentRequest (DGDR) is a Kubernetes Custom Resource that serves as the primary interface for users to request model deployments with specific performance and resource constraints. You specify:

• What model you want to deploy (model)
• How it should perform (SLA targets: ttft, itl)
• Where it should run (optional GPU preferences)
• Which backend to use (backend: vllm, sglang, or trtllm)
• Which images to use (profilingConfig.profilerImage, deploymentOverrides.workersImage)

The Dynamo Operator watches for DGDRs and automatically:

1. Discovers available GPU resources in your cluster
2. Runs profiling (online or offline) to find optimal configurations
3. Generates an optimized DynamoGraphDeployment (DGD) configuration
4. Deploys the DGD to your cluster

Relationship to DGD:

• DGDR: High-level “intent” - what you want deployed
• DGD: Low-level “implementation” - how it’s deployed

Support Matrix

The profiler sweeps over the following parallelization mappings for prefill and decode:

[!NOTE] Exact model x parallelization mapping support is dependent on the backend. The profiler does not guarantee that the recommended P/D engine configuration is supported and bug-free by the backend.

Deployment

Kubernetes Deployment (DGDR)

The recommended deployment method is through DGDRs. Sample configurations are provided in benchmarks/profiler/deploy/:

Container Images

Each DGDR requires container images for profiling and deployment:

• profilingConfig.profilerImage (Required): Container image for the profiling job. Must contain the profiler code and dependencies.
• deploymentOverrides.workersImage (Optional): Container image for DGD worker components (frontend, workers, planner). If omitted, uses image from the base config file.

1
spec:
2
  profilingConfig:
3
    profilerImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"
4
  deploymentOverrides:
5
    workersImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"

Quick Start: Deploy with DGDR

Step 1: Create Your DGDR

Use a sample configuration or create your own:

1
apiVersion: nvidia.com/v1alpha1
2
kind: DynamoGraphDeploymentRequest
3
metadata:
4
  name: my-model-profiling
5
spec:
6
  model: "Qwen/Qwen3-0.6B"
7
  backend: vllm
8
  profilingConfig:
9
    profilerImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"
10
    config:
11
      sla:
12
        isl: 3000
13
        osl: 150
14
        ttft: 200.0
15
        itl: 20.0
16
  deploymentOverrides:
17
    workersImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"
18
  autoApply: true

Step 2: Apply the DGDR

$
export NAMESPACE=your-namespace
$
kubectl apply -f my-profiling-dgdr.yaml -n $NAMESPACE

Step 3: Monitor Progress

$
# View status
$
kubectl get dgdr -n $NAMESPACE
$
$
# Detailed status
$
kubectl describe dgdr my-model-profiling -n $NAMESPACE
$
$
# Watch profiling job logs
$
kubectl logs -f job/profile-my-model-profiling -n $NAMESPACE

DGDR Status States:

• Pending: Initial state, preparing to profile
• Profiling: Running profiling job (20-30 seconds for AIC, 2-4 hours for online)
• Deploying: Generating and applying DGD configuration
• Ready: DGD successfully deployed and running
• Failed: Error occurred (check events for details)

Step 4: Access Your Deployment

$
# Find the frontend service
$
kubectl get svc -n $NAMESPACE | grep frontend
$
$
# Port-forward to access locally
$
kubectl port-forward svc/<deployment>-frontend 8000:8000 -n $NAMESPACE
$
$
# Test the endpoint
$
curl http://localhost:8000/v1/models

[!NOTE] DGDRs are immutable. To update SLAs or configuration, delete the existing DGDR and create a new one.

Direct Script Execution

For advanced use cases or local development:

$
python -m benchmarks.profiler.profile_sla \
>
  --backend vllm \
>
  --config path/to/disagg.yaml \
>
  --model meta-llama/Llama-3-8B \
>
  --ttft 200 --itl 15 \
>
  --isl 3000 --osl 150 \
>
  --min-num-gpus 1 \
>
  --max-num-gpus 8

Profiling Method

The profiler follows a 5-step process:

1. Hardware Setup: Uses defaults or user-specified hardware configuration. Optionally, cluster-scoped operators can enable automatic GPU discovery to detect specifications from cluster nodes.
2. Identify Sweep Ranges: Automatically determine minimum and maximum number of GPUs per engine. Minimum is determined by the model size and GPU VRAM. Maximum is set to one node for dense models and 4 nodes for MoE models.
3. Parallelization Mapping Sweep: Test performance of engines with different parallelization mappings using the input ISL and OSL.
   • For dense models, test different TP sizes for both prefill and decode.
   • For MoE models (SGLang), evaluate both TEP and DEP as candidates for prefill and decode.
   • Prefill:
     • TP/TEP: Measure TTFT with batch size = 1 (assuming ISL is long enough to saturate compute) without KV reuse.
     • DEP: Attention uses data parallelism. Send a single burst with total concurrency attention_dp_size × attn_dp_num_req_ratio (defaults to 4) and compute the reported TTFT as time_to_first_token.max / attn_dp_num_req_ratio from the AIPerf summary of that burst.
   • Decode: Measure the ITL under different numbers of in-flight requests, from 1 to the maximum the KV cache can hold. To measure ITL without being affected by piggy-backed prefill requests, the script enables KV-reuse and warms up the engine by issuing the same prompts before measuring.
4. Recommendation: Select optimal parallelization mapping for prefill and decode that achieves the highest per-GPU throughput while adhering to the SLA on TTFT and ITL.
5. In-Depth Profiling on the Recommended P/D Engine: Interpolate TTFT with ISL and ITL with active KV cache and decode context length for more accurate performance estimation.
   • Prefill: Measures TTFT and throughput per GPU across different input lengths with batch size=1.
   • Decode: Measures ITL and throughput per GPU under various KV cache loads and decode context lengths.

AIPerf on Real Engines

Profiles your model by creating real test deployments in Kubernetes and measuring their performance.

• Duration: 2-4 hours
• Accuracy: Highest (real measurements)
• GPU Requirements: Full access to test different parallelization mappings
• Backends: vLLM, SGLang, TensorRT-LLM

1
profilingConfig:
2
  config:
3
    sweep:
4
      useAiConfigurator: false  # Default

AI Configurator Simulation

Uses performance simulation to rapidly estimate optimal configurations without running real deployments.

• Duration: 20-30 seconds
• Accuracy: Estimated (may have errors for unusual configurations)
• GPU Requirements: None
• Backends: TensorRT-LLM only (vLLM/SGLang coming soon)

1
profilingConfig:
2
  config:
3
    sweep:
4
      useAiConfigurator: true
5
      aicSystem: h200_sxm
6
      aicHfId: Qwen/Qwen3-32B
7
      aicBackendVersion: "0.20.0"      # TRT-LLM version simulated by AIC

[!NOTE] aicBackendVersion specifies the TensorRT-LLM version that AI Configurator simulates. See the AI Configurator supported features for available versions.

Currently supports:

• Backends: TensorRT-LLM (versions 0.20.0, 1.0.0rc3, 1.0.0rc6)
• Systems: H100 SXM, H200 SXM, B200 SXM, GB200 SXM, A100 SXM
• Models: Wide range including GPT, Llama, Mixtral, DeepSeek, Qwen, and more

See AI Configurator documentation for the full list.

Automatic GPU Discovery

Cluster-scoped operators can optionally enable automatic GPU discovery:

1
spec:
2
  enableGpuDiscovery: true

This is only available with cluster-scoped operators (namespaceRestriction.enabled=false) as it requires cluster-wide node access permissions.

Configuration

DGDR Configuration Structure

All profiler configuration goes under spec.profilingConfig.config:

1
apiVersion: nvidia.com/v1alpha1
2
kind: DynamoGraphDeploymentRequest
3
metadata:
4
  name: my-deployment
5
spec:
6
  model: "Qwen/Qwen3-0.6B"
7
  backend: vllm
8
9
  profilingConfig:
10
    profilerImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"
11
    configMapRef:                  # Optional: base DGD config
12
      name: my-config
13
      key: disagg.yaml
14
15
    config:
16
      sla: { ... }
17
      hardware: { ... }
18
      sweep: { ... }
19
      planner: { ... }
20
21
  deploymentOverrides:
22
    workersImage: "nvcr.io/nvidia/ai-dynamo/vllm-runtime:0.9.0"

SLA Configuration (Required)

1
sla:
2
  isl: 3000      # Average input sequence length (tokens)
3
  osl: 150       # Average output sequence length (tokens)
4
  ttft: 200.0    # Target Time To First Token (milliseconds)
5
  itl: 20.0      # Target Inter-Token Latency (milliseconds)

• ISL/OSL: Based on your expected traffic patterns
• TTFT: First token latency target (lower = more GPUs needed, affects prefill engine)
• ITL: Token generation latency target (lower = more GPUs needed, affects decode engine)
• Trade-offs: Tighter SLAs require more GPU resources

Hardware Configuration (Optional)

1
hardware:
2
  minNumGpusPerEngine: 2      # Auto-determined from model size and VRAM if not provided
3
  maxNumGpusPerEngine: 8      # Maximum GPUs to test
4
  numGpusPerNode: 8           # GPUs per node (for multi-node MoE)
5
  gpuType: h200_sxm           # GPU type hint (informational, auto-detected)

• minNumGpusPerEngine: Skip small TP sizes if your model is large
• maxNumGpusPerEngine: Limit search space or work around constraints (e.g., AIC attention heads)
• numGpusPerNode: Determine the upper bound of GPUs per node for dense models and configure Grove for multi-node MoE engines
• gpuType: Informational only, auto-detected by the controller. For AI Configurator, use aicSystem in the sweep configuration instead

[!TIP] If you don’t specify hardware constraints, the controller auto-detects based on your model size and available cluster resources.

Sweep Configuration (Optional)

1
sweep:
2
  useAiConfigurator: false              # Use real profiling (default)
3
  prefillInterpolationGranularity: 16   # Samples for prefill TTFT curve
4
  decodeInterpolationGranularity: 6     # Samples for decode ITL curve

• useAiConfigurator: Set to true for 20-30 second profiling (TensorRT-LLM only)
• prefillInterpolationGranularity: Samples for prefill TTFT curve (lower = faster but less accurate)
• decodeInterpolationGranularity: Samples for decode ITL curve. Since ITL interpolation is 3D and takes longer, we default to fewer samples. Increasing this value may quadratically increase profiling time.

AI Configurator Configuration

Required if useAiConfigurator: true:

1
sweep:
2
  useAiConfigurator: true
3
  aicSystem: h200_sxm              # h100_sxm, h200_sxm, b200_sxm, gb200_sxm, a100_sxm
4
  aicHfId: Qwen/Qwen3-32B         # HuggingFace model ID
5
  aicBackendVersion: "0.20.0"      # TensorRT-LLM version

Planner Configuration (Optional)

Pass arguments to the SLA planner:

1
planner:
2
  planner_min_endpoint: 2                    # Minimum endpoints to maintain
3
  planner_adjustment_interval: 60            # Adjustment interval (seconds)
4
  planner_load_predictor: linear             # Load prediction method

[!NOTE] Planner arguments use planner_ prefix. See SLA Planner documentation for full list.

Model Cache PVC (Advanced)

For large models, use a pre-populated PVC containing model weights instead of downloading from HuggingFace:

1
deployment:
2
  modelCache:
3
    pvcName: "model-cache"
4
    pvcPath: "hub/models--deepseek-ai--DeepSeek-R1"
5
    mountPath: "/opt/model-cache"

Requirements:

• The PVC must exist in the same namespace as the DGDR
• The model weights must be accessible at {mountPath}/{pvcPath}

Engine Configuration (Auto-configured)

The controller automatically injects these from high-level fields:

1
# You specify:
2
spec:
3
  model: "Qwen/Qwen3-0.6B"
4
  backend: vllm
5
6
# Controller auto-injects:
7
profilingConfig:
8
  config:
9
    deployment:
10
      model: "Qwen/Qwen3-0.6B"
11
    engine:
12
      backend: vllm
13
      config: /path/to/configmap

You should not manually set deployment.model or engine.backend in profilingConfig.config.

Using Existing DGD Configs (ConfigMap)

Reference an existing DGD config via ConfigMap:

$
kubectl create configmap my-config \
>
  --from-file=disagg.yaml=/path/to/your/disagg.yaml \
>
  --namespace $NAMESPACE \
>
  --dry-run=client -o yaml | kubectl apply -f -

1
profilingConfig:
2
  configMapRef:
3
    name: my-config
4
    key: disagg.yaml

The profiler uses the DGD config as a base template, then optimizes it based on your SLA targets.

CLI Arguments

[!NOTE] CLI arguments map to DGDR config fields: --min-num-gpus = hardware.minNumGpusPerEngine, --max-num-gpus = hardware.maxNumGpusPerEngine, --use-ai-configurator = sweep.useAiConfigurator. See DGDR Configuration Structure for all field mappings.

Integration

With SLA Planner

The Profiler generates interpolation data that the SLA Planner uses for autoscaling decisions.

Prefill Interpolation (selected_prefill_interpolation/raw_data.npz):

• prefill_isl: 1D array of input sequence lengths tested
• prefill_ttft: 1D array of TTFTs (ms) at each ISL
• prefill_thpt_per_gpu: 1D array of throughput (tokens/s/GPU) at each ISL

Decode Interpolation (selected_decode_interpolation/raw_data.npz):

• max_kv_tokens: Total KV tokens capacity in decode engine
• x_kv_usage: 1D array of active KV usage percentages [0, 1]
• y_context_length: 1D array of average context lengths tested
• z_itl: 1D array of ITLs (ms) at each (KV usage, context length) point
• z_thpt_per_gpu: 1D array of throughput (tokens/s/GPU) at each point

With Dynamo Operator

When using DGDR, the Dynamo Operator:

1. Creates profiling jobs automatically
2. Stores profiling data in ConfigMaps (planner-profile-data)
3. Generates optimized DGD configurations
4. Deploys the DGD with SLA Planner integration

The generated DGD is tracked via labels:

1
metadata:
2
  labels:
3
    dgdr.nvidia.com/name: my-deployment
4
    dgdr.nvidia.com/namespace: your-namespace

With Observability

Monitor profiling jobs:

$
kubectl logs -f job/profile-<dgdr-name> -n $NAMESPACE
$
kubectl describe dgdr <name> -n $NAMESPACE

Advanced Topics

Manual Deployment Control

Disable auto-deployment to review the generated DGD before applying:

1
spec:
2
  autoApply: false

Then manually extract and apply:

$
# Extract generated DGD from DGDR status
$
kubectl get dgdr my-deployment -n $NAMESPACE -o jsonpath='{.status.generatedDeployment}' | kubectl apply -f -
$
$
# Or save to file for review
$
kubectl get dgdr my-deployment -n $NAMESPACE -o jsonpath='{.status.generatedDeployment}' > my-dgd.yaml

Mocker Deployment

Deploy a mocker deployment that simulates engines without GPUs:

1
spec:
2
  model: <model-name>
3
  backend: trtllm
4
  useMocker: true    # Deploy mocker instead of real backend
5
  autoApply: true

Profiling still runs against the real backend to collect performance data. The mocker uses this data to simulate realistic timing behavior. Useful for large-scale experiments, testing Planner behavior, and validating configurations.

Accessing Profiling Artifacts

By default, profiling data is stored in ConfigMaps. For detailed artifacts (plots, logs, raw data), attach a PVC:

1
profilingConfig:
2
  outputPVC: "dynamo-pvc"

ConfigMaps (always created):

• dgdr-output-<name>: Generated DGD configuration
• planner-profile-data: Profiling data for Planner (JSON)

PVC artifacts (optional):

• Performance plots (PNGs)
• DGD configurations for each profiled deployment
• AIPerf profiling artifacts
• Raw profiling data (.npz files)
• Profiler logs

Access PVC results:

$
kubectl apply -f deploy/utils/manifests/pvc-access-pod.yaml -n $NAMESPACE
$
kubectl wait --for=condition=Ready pod/pvc-access-pod -n $NAMESPACE --timeout=60s
$
kubectl cp $NAMESPACE/pvc-access-pod:/data ./profiling-results
$
kubectl delete pod pvc-access-pod -n $NAMESPACE

Output Performance Plots

The profiler generates plots to visualize performance data:

Parallelization Mapping Sweep Plots:

• prefill_performance.png: TTFT vs Parallelization Mapping size
• decode_performance.png: ITL vs Parallelization Mapping size and in-flight requests

In-Depth Profiling Plots:

• selected_prefill_interpolation/prefill_ttft_interpolation.png: TTFT vs ISL
• selected_prefill_interpolation/prefill_throughput_interpolation.png: Throughput vs ISL
• selected_decode_interpolation/decode_itl_interplation.png: ITL vs KV usage and context length
• selected_decode_interpolation/decode_throughput_interpolation.png: Throughput vs KV usage and context length

Runtime Profiling (SGLang)

SGLang workers expose profiling endpoints for runtime performance analysis:

$
# Start profiling
$
curl -X POST http://localhost:9090/engine/start_profile \
>
  -H "Content-Type: application/json" \
>
  -d '{"output_dir": "/tmp/profiler_output"}'
$
$
# Run inference requests...
$
$
# Stop profiling
$
curl -X POST http://localhost:9090/engine/stop_profile

View traces using Chrome’s chrome://tracing, Perfetto UI, or TensorBoard.

Troubleshooting

Profiling Takes Too Long

Solution 1: Use AI Configurator for rapid profiling (TensorRT-LLM only):

1
sweep:
2
  useAiConfigurator: true

Solution 2: Reduce search space:

1
hardware:
2
  minNumGpusPerEngine: 4  # Skip TP1, TP2
3
  maxNumGpusPerEngine: 8  # Don't test beyond TP8

SLA Cannot Be Met

Symptoms: Profiler reports no configuration meets targets

Solutions:

1. Relax SLA targets (increase TTFT/ITL)
2. Add more GPU resources
3. Try a different backend
4. Use a smaller model

AI Configurator: Attention Head Constraint Error

Symptoms: Profiling fails with error:

AssertionError: num_heads <N> should be divisible by tp_size <M> and the division result should be >= 4

Cause: AI Configurator requires ≥4 attention heads per GPU. Small models with few heads cannot use high TP sizes.

Affected Models:

• Qwen3-0.6B (16 heads): Max TP = 4
• GPT-2 (12 heads): Max TP = 3
• Most models <1B parameters: May hit this constraint

Solution: Limit maxNumGpusPerEngine:

1
hardware:
2
  maxNumGpusPerEngine: 4  # For Qwen3-0.6B (16 heads / 4 = max TP of 4)

Calculate Max TP: max_tp = num_attention_heads / 4

[!NOTE] This is an AI Configurator limitation. Online profiling doesn’t have this constraint.

Image Pull Errors

Symptoms: ErrImagePull or ImagePullBackOff

Solution: Ensure image pull secrets are configured:

$
kubectl create secret docker-registry nvcr-imagepullsecret \
>
  --docker-server=nvcr.io \
>
  --docker-username='$oauthtoken' \
>
  --docker-password=<NGC_API_KEY> \
>
  --namespace <your-namespace>

Out of Memory During Profiling

Symptoms: OOM errors in profiling jobs

Solutions:

1. Reduce gpu_memory_utilization in engine config
2. Reduce --max-context-length
3. Skip larger TP configurations
4. Use fewer GPUs per test

Unsupported Parallelization Mapping in Backend

Symptoms: Startup/runtime error in the backend (e.g., prime number of attention heads constraining TP to 1, or backend not supporting different TP sizes for prefill and decode).

Solutions:

1. Contact the backend to add support and bump backend version in Dynamo
2. Constrain the max and min number of GPUs per engine to the supported range

See Also

• Profiler Examples - Complete DGDR YAML examples
• SLA Planner Guide - End-to-end deployment workflow
• SLA Planner Architecture - How the Planner uses profiling data
• DGDR API Reference - DGDR specification
• Profiler Arguments Reference - Full CLI reference