jetson-llm-benchmark

Benchmark Jetson LLM serving and return structured latency and throughput metrics.

110|19|Updated May 25, 2026
One-click install
npx skills add https://github.com/NVIDIA-AI-IOT/jetson-device-skills --skill jetson-llm-benchmark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-llm-benchmark
Source: https://github.com/NVIDIA-AI-IOT/jetson-device-skills/tree/main/skills/jetson-llm-benchmark
Command: npx skills add https://github.com/NVIDIA-AI-IOT/jetson-device-skills --skill jetson-llm-benchmark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It removes the guesswork from measuring Jetson-hosted model serving by producing repeatable latency and throughput benchmarks in a structured format that is easy to compare across runs.

Core Features & Use Cases

  • vLLM concurrency sweeps: Measure TTFT, ITL, TPOT, throughput, and end-to-end latency for an already running OpenAI-compatible vLLM server.
  • llama.cpp GGUF benchmarking: Run Jetson-appropriate llama.cpp benchmarks for local GGUF models through the NVIDIA-AI-IOT container workflow.
  • Ollama performance checks: Benchmark a reachable Ollama daemon with single-stream requests and capture prompt, generation, and throughput metrics.
  • Use Case: Compare before-and-after tuning changes, validate power-mode choices, and confirm whether a model deployment is memory-bound or decode-bound on a live Jetson device.

Quick Start

Ask the agent to benchmark the running Jetson LLM service with the matching runtime wrapper, using the served model ID or GGUF path and then report the resulting JSON metrics.

Frequently Asked Questions about jetson-llm-benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I benchmark LLM serving throughput and latency on a Jetson device?

Benchmark Jetson LLM serving performance by executing runtime wrapper scripts against a live service to return structured latency and throughput metrics. It measures TTFT, ITL, TPOT, and end-to-end latency for vLLM, llama.cpp, and Ollama deployments.

Can I measure Ollama single-stream performance and capture generation metrics on Jetson?

Ollama performance checks benchmark a reachable daemon with single-stream requests to capture prompt, generation, and throughput metrics. This validates whether your model deployment is memory-bound or decode-bound on the live Jetson device.

How do I run a vLLM concurrency sweep to measure TTFT and TPOT?

vLLM concurrency sweeps measure TTFT, ITL, TPOT, throughput, and end-to-end latency for an already running OpenAI-compatible vLLM server. The benchmark requires the matching wrapper script, validated model identifiers, and live Jetson device detection.

Does this benchmarking approach work with local GGUF models using llama.cpp?

llama.cpp GGUF benchmarking runs Jetson-appropriate measurements for local models through the NVIDIA-AI-IOT container workflow. You must provide valid GGUF paths and ensure live device detection for SKU, L4T, and container metadata.

What do I need to detect before benchmarking Jetson LLM serving performance?

Live device detection is required to identify SKU, L4T, and container metadata before benchmarking Jetson LLM serving performance. You also need the matching wrapper scripts and validated model identifiers or GGUF paths to execute the runs.

When should I benchmark Jetson LLM serving to compare before-and-after tuning changes?

Benchmark Jetson LLM serving to compare before-and-after tuning changes, validate power-mode choices, and confirm memory or decode bottlenecks. This removes guesswork by producing repeatable latency and throughput metrics in a structured format.