nvidia-nlp-operator

Benchmarks GEMM, Conv2d, long-tail, and Transformer Block operators on NVIDIA GPUs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Measuring CUDA operator performance on NVIDIA GPUs requires manual container setup, compilation with nvcc and cuDNN, baseline generation, and metric collection, which is error-prone and hard to reproduce. This Skill automates the full evaluation workflow so results are deterministic and comparable. ## Core Features & Use Cases - Operator Benchmarking: Runs GEMM (FP16/FP32 with tensor cores), Conv2d, 100+ long-tail operators from LongTail-Bench, and Transformer Encoder/Decoder Block inference latency tests. - Deterministic Result Collection: Ships collector scripts that validate CSV outputs, verify run tokens and workload fingerprints, and emit Result Contract 2.0 JSON with summary metrics (avg, p50, p95, min, max latency). - Containerized Workflow: Guides Docker container startup with GPU mounts, direct nvcc compilation, baseline generation, and test execution with strict failure checks. - Use Case: Ask the agent to generate GEMM operator baselines on an NVIDIA GPU; it launches the container, compiles the CUDA kernels, runs the FP16/FP32 test suites, and produces a validated result.json. ## Quick Start Ask the agent to generate GEMM operator baseline values on an NVIDIA GPU and collect the performance metrics.

Frequently Asked Questions about nvidia-nlp-operator

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

FAQPage Schema
How do I benchmark GEMM operator performance on NVIDIA GPUs?

Compile cuda_gemm.cpp directly with nvcc -O3 -lcublas, then run test_gemm.py against the gemm_f16.csv and gemm_f32.csv parameter files in baseline mode. The collector script converts results into a Result Contract 2.0 JSON with latency statistics.

How to run Conv2d benchmarks when cuDNN linking fails?

Resolve the actual cuDNN library path from the nvidia.cudnn Python package and link with -l:<actual filename> plus an rpath, since the image may only ship versioned libcudnn.so.* files. Never fall back to an old prebuilt binary after a link failure.

What operators does this NVIDIA benchmark support?

It supports five categories: GEMM (FP16/FP32), Conv2d (FP16/FP32), over 100 long-tail operators from LongTail-Bench, Transformer Encoder/Decoder Block inference latency, and NCCL or OSU-based communication operators requiring multi-node environments.

Does the Transformer Block test use training or inference mode?

It uses FP32 inference mode with eval() and torch.inference_mode(), measuring average latency over 1000 iterations after 20 warmup iterations with CUDA synchronization. The project's original test.py is not used because it runs in train mode without proper timing boundaries.

Why does the benchmark report success without running kernels?

This false positive happens when the top-level CMake fails (it requires cuDNN that GEMM images may lack) and stale CSV baselines are reused. The Skill prevents this by requiring direct nvcc compilation and verifying CSV modification timestamps before collection.

What are the hardware requirements for communication operator tests?

Communication operator tests require a multi-node, multi-GPU environment with SSH passwordless login, InfiniBand or high-speed interconnects, and OpenMPI/UCX installed. Single-GPU machines can run GEMM, Conv2d, long-tail, and Transformer Block tests only.