Agent skill · NVIDIA
doca-bench
Run `doca_bench` (DOCA 2.7.0 or newer) to measure throughput, bulk latency, precision latency, or maximum bandwidth for RDMA, Compress, AES-GCM, SHA, DMA, EC, Ethernet, Comch, or GPUNetIO on a host or BlueField Arm. Use it to discover enabled benchmark libraries, capture a reproducible command/version/device/environment baseline, compare stable runs against a declared tolerance, or diagnose configuration, device-binding, workload-precondition, and measurement failures. Trigger for requests such as measuring BlueField compression speed, NIC RDMA throughput, crypto latency, or a pre-upgrade baseline. Do not use for application end-to-end timing, custom benchmark code, DOCA installation, or binary patches.
What it needs
About 7k tokens when loaded.
What this skill does
DOCA Bench (docabench) Where to start: This is a tool skill for invoking docabench, the cross-library micro-benchmark harness. Open TASKS.md and start at configure for the three-axis decision (target library × workload shape × measurement axis), then run for the smoke-before-bulk flow. Open CAPABILITIES.md when the question is what docabench can measure, which DOCA libraries it can drive, or how to interpret throughput / latency / op-rate output without fooling yourself on warm-up or steady-state. If DOCA is not installed yet, route to doca-setup first; if the install version is < 2.7.0, docabench is not shipped on this host. Example questions this skill answers well The CLASSES of docabench questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance. "What does this DOCA library actually deliver on this device?" — worked example: "throughput of DOCA Compress on my BlueField-3". Answered by the three-axis configuration in CAPABILITIES.md ## Capabilities and modes the smoke-before-bulk flow in TASKS.md ## run. The same shape answers "send-side throughput of DOCA RDMA" — docabench is cross-library, not single-library. "Which DOCA libraries can docabench actually drive on this install?" — worked example: "is docasha enumerable on a granular-build install". Answered by the built-in query system surfaced in CAPABILITIES.md ## Capabilities and modes TASKS.md ## configure step 2 (probe-before-bench). Empty enumeration = library not installed, not bench failure. "Is this number reliable, or did I miss the warm-up?" — worked example: "why does my first-second number differ from my steady-state number". Answered by the measurement-soundness overlay in CAPABILITIES.md ## Error taxonomy layer 5 + TASKS.md ## test (the eval-loop overlay treats warm-up / steady-state / outliers as re-iteration triggers, not one-shot facts). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-bench