Agent skill · data analytics · 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.
Why this skill is useful
Provides specific commands and configurations for measuring performance metrics of DOCA libraries that the AI wouldn't reliably generate on its own.
What it needs
Requires doca installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
DOCA Bench (docabench) Examples "What does this DOCA library actually deliver on this device?" — this is in scope. Stay on docabench; do not write a custom microbenchmark. "Which DOCA libraries can docabench drive on this install?" — probe the built-in query first; empty enumeration is a missing library, not a bench failure. Instructions Follow Loading order below. Open the tasks companion for configure / run / debug. Open the capabilities companion for modes and measurement soundness. Do not open every companion file. Where to start: This is a tool skill for invoking docabench, the cross-library micro-benchmark harness. Open the tasks companion and start at configure for the three-axis decision (target library × workload shape × measurement axis), then run for the smoke-before-bulk flow. Open the capabilities companion 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/SKILL.md 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 the capabilities companion the smoke-before-bulk flow in the tasks companion. 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". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-bench