nvidia-nlp-inference

Benchmarks SGLang-served HuggingFace text models on NVIDIA GPUs for throughput and latency.

7|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/DeepLink-org/DeepEval-Skills --skill nvidia-nlp-inference-deeplink-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nvidia-nlp-inference
Source: https://github.com/DeepLink-org/DeepEval-Skills/tree/main/skills/NVIDIA/nlp/nvidia-nlp-inference
Command: npx skills add https://github.com/DeepLink-org/DeepEval-Skills --skill nvidia-nlp-inference-deeplink-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sglang, and includes scripts (resource) and references (resource) components.

What problem does it solve? Evaluating LLM inference performance on NVIDIA GPUs requires coordinating container setup, SGLang server lifecycle, offline load testing, and metric extraction, which is error-prone when done manually. This Skill standardizes the entire workflow so results are comparable across models and runs. ## Core Features & Use Cases - Unified serve/bench/calc pipeline: Prebuilt scripts launch SGLang servers, run fixed-seed offline benchmarks with sglang.bench_serving, and parse logs into a schema-versioned result.json with throughput, TTFT, TPOT, ITL, and end-to-end latency metrics. - Model profiles and multi-host support: A profile registry (generic, DeepSeek-R1, Llama-1/2 variants) defines per-model TP, sequence lengths, and precision matrices, with rank-aware multi-node execution over NCCL/NVSHMEM. - Use Case: Ask the agent to evaluate DeepSeek-R1 inference on an 8-GPU node; the Skill mounts model and dataset directories into the container, serves the model with TP=8, runs 1000 prompts at 2048 input/output tokens, and produces a validated result.json. ## Quick Start Ask the agent to evaluate the inference throughput and latency of your HuggingFace model on NVIDIA GPUs using the nvidia-nlp-inference skill with the mounted model and dataset directories.

Frequently Asked Questions about nvidia-nlp-inference

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

FAQPage Schema
How do I benchmark LLM inference throughput with SGLang on NVIDIA GPUs?

Launch the SGLang server with serve.sh using the profile's TP and GPU IDs, then run bench.sh which invokes sglang.bench_serving with fixed input length, output length, and prompt count. Finally run calc.sh to parse the benchmark log into a result.json with throughput and latency metrics.

How to run multi-node SGLang inference benchmarks across two machines?

Use serve_multi_host.sh on every node with MASTER_ADDR, MASTER_PORT, NNODES, NODE_RANK, and GPUS_PER_NODE set by the executor; TP becomes NNODES times GPUS_PER_NODE. Only rank0 runs bench.sh and calc.sh, and NCCL/NVSHMEM network variables must come from the model profile.

What metrics does SGLang bench_serving report for LLM inference?

The benchmark reports output token throughput, total token throughput, concurrency, mean end-to-end latency, mean TTFT, mean TPOT, and mean ITL. The calc.sh script also derives output tokens per second per GPU by dividing throughput by TP.

Can I evaluate FP16 and INT8 quantized Llama models in one run?

Yes, Llama profiles use scripts/llama/run_precision_matrix.sh, which serves and benchmarks each precision separately using --dtype float16 and --torchao-config int8wo. The fp16 result becomes the primary result.json while int8 results are kept in a subdirectory.

Why does the SGLang benchmark fail with connection refused?

Connection refused means the server was not ready when bench.sh started; serve.sh waits for the /v1/models endpoint rather than just port listening. Check serve.log for model loading errors and increase READY_TIMEOUT for large models.

What dataset format is required for SGLang offline benchmarking?

The benchmark requires a local ShareGPT-format JSON file mounted into the container's dataset directory. Scripts prefer the profile-specified filename, then the standard ShareGPT_V3 file, then the first JSON found; no dataset is downloaded from the network.