Generated banner for Doca Perftest
Generated logo for Doca Perftest

Doca Perftest

NVIDIAOfficialCreated by NVIDIA

  • Skill
  • Tool integration
  • Software development
  • Apache-2.0
  • Medium risk

From the author

Use this skill when the user is running DOCA Perftest (doca_perftest), the RDMA benchmark that measures bandwidth, message rate and latency for RDMA verbs, point-to-point or across a cluster, with an optional DOCA Verbs backend (-r dv) or GPUNetIO engine (--engine gpunetio). Trigger even when the user does not say "DOCA Perftest" — implicit phrasings include "how do I benchmark RDMA write bandwidth with DOCA", "run ib_write_bw but across 8 nodes", "perftest says the device is busy", "my latency numbers differ between client and server", "launch the server over SSH", or "run an all-to-all RDMA test from a JSON scenario". Refuse and route elsewhere for DOCA install (doca-setup), DOCA Bench (doca-bench), and application-level throughput.
— the description by NVIDIA

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The doca-perftest skill assists users in executing and interpreting results from the doca_perftest utility, a performance benchmarking tool for RDMA verbs. It covers point-to-point and multi-node testing scenarios, including the use of DOCA Verbs and GPUNetIO backends. The skill provides instructions for configuring benchmarks, managing multi-node orchestration, and troubleshooting common issues like device contention or inconsistent latency metrics.

What it does

  • Guides users through running RDMA bandwidth, message rate, and latency benchmarks.
  • Supports configuration for point-to-point and cluster-wide multi-node testing.
  • Facilitates comparison between IBV, DOCA Verbs, and GPUNetIO engine backends.
  • Assists in interpreting benchmark results and diagnosing performance discrepancies.
  • Provides troubleshooting steps for common runtime errors like device busy states.

When to use it

  • When you need to measure RDMA performance metrics on systems with DOCA installed.
  • When performing multi-node benchmarking using JSON scenarios or traffic patterns.
  • When comparing different RDMA drivers or backends within the DOCA environment.
  • When debugging inconsistent latency or bandwidth numbers between client and server nodes.

Advantages

  • Streamlines the execution of complex multi-node RDMA performance tests.
  • Provides clear guidance on backend selection for optimized testing.
  • Helps identify and resolve common configuration issues in RDMA benchmarking.
  • Standardizes the approach to performance measurement across DOCA-enabled clusters.

Usage examples

“Run a point-to-point RDMA write bandwidth test.”
The agent provides the command structure using -v write -m bw, explaining how to coordinate the server and client nodes.
“Benchmark 16 nodes at once and get one report.”
The agent explains how to use a JSON scenario or the --traffic_pattern flag to aggregate performance data across the cluster.
“My latency numbers differ between client and server.”
The agent guides the user to check NUMA placement, core affinity, and consistency in message sizes and verb types.
“perftest says the device is busy”
The agent provides troubleshooting steps to identify and clear processes holding the RDMA device.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/doca-perftest/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip doca-perftest.zip -d .agents/skills

Documentation by NVIDIA

DOCA Perftest

When to load this skill

Load this skill when the user wants to — or the agent needs to — run doca_perftest on a host with DOCA installed. Concretely:

  • Measuring RDMA bandwidth, message rate, or latency between two hosts (point-to-point) with a verb such as write / read / send.

  • Running the same benchmark across many nodes — JSON scenario or --traffic_pattern (pair-wise, all-to-all), orchestrated over OpenMPI / passwordless SSH.

  • Comparing the IBV and DOCA Verbs backends (-r ibv vs -r dv) or driving the GPUNetIO engine (--engine gpunetio).

  • Interpreting a run: client-vs-server number drift, "device busy", inconsistent latency across runs.

Do not load this skill for DOCA install (doca-setup), the doca-bench harness, Flow pipeline tuning (doca-flow-tune), or application-level throughput.

Examples

  • "Measure RDMA write bandwidth between two ConnectX-7 hosts with 64 KB messages." Point-to-point: run the server, then the client with -n.

  • "I need latency across 16 nodes, all-to-all." Multi-node: JSON scenario or --traffic_pattern, with OpenMPI.

  • "Compare the IBV and DOCA Verbs drivers on the same device." Same command, -r ibv vs -r dv.

Instructions

Follow the loading order below. Open TASKS.md for the commands and CAPABILITIES.md for what the tool can measure and what it does not.

Where to start: DOCA Perftest is the DOCA 3.5 replacement for legacy ib_write_bw / ib_send_lat plus the orchestration scripts used to run them on many nodes. Start at TASKS.md ## point-to-point for a first run. Use ## multi-node for scenarios and ## debug when a run fails or the numbers look wrong.

If DOCA is not installed, route to doca-setup/SKILL.md. Client and server must run the same DOCA Perftest version; check with doca-version/SKILL.md before comparing numbers across hosts. If the question is about GPU-initiated RDMA in the user's own code, route to doca-gpunetio/SKILL.md.

Example questions this skill answers well

  • "Run a point-to-point RDMA write bandwidth test." Use -d <dev> -n <server> -v write -m bw -s <size> -D <sec>; the client coordinates the server side over SSH (requires SSH key exchange set up beforehand).

  • "Benchmark 16 nodes at once and get one report." Use a JSON scenario or --traffic_pattern; the report aggregates per device, node and test.

  • "Latency differs between runs." Check the latency mode, the core and NUMA placement, and whether both sides use the same message size and verb.

Loading order

  1. This file for scope and routing.

  2. TASKS.md for the exact command for the job you are doing.

  3. CAPABILITIES.md when you need to know whether a verb, driver, memory type or traffic pattern is supported.

Do not open every companion file.

Scope boundaries

  • Installs and driver packages: doca-setup/SKILL.md.

  • Version matching across client, server and DOCA release: doca-version/SKILL.md.

  • Any change to NIC or eswitch state, firmware, or host kernel settings (hugepages, IOMMU, PCIe rebind): follow doca-hardware-safety/SKILL.md first.

  • Failure diagnosis: doca-debug/SKILL.md for the layer ladder, then the TASKS.md ## debug anchor here.

  • Upstream CPU-initiated ib_write_bw: this tool replaces it on DOCA 3.5; do not mix the two in one comparison without saying so.

Files

BENCHMARK.md

Skill Benchmark: doca-perftest

✅ Overall verdict: PASS — Recommended for publication

Publication Recommendation

Recommended for publication based on the completed evaluation evidence in this report.

Evaluation Metadata

  • Skill: doca-perftest

  • Validation status: passed

  • Evaluation date: 2026-10-28

  • Evaluator version: 1.6.2

  • Agents: Claude Code (aws/anthropic/bedrock-claude-opus-5-5), Codex (openai/openai/gpt-6.1-sol)

  • Tasks: 5 evaluation tasks (4 positive, 1 negative)

  • Dataset digest: sha256:43ee35f3cdeb638111792c9166ce0f14e4d89def25865872b518f9029087d974 (skill-evaluator-dataset-snapshot/1)

  • Attempts per task: 1

  • Environment: k8s-sandbox

  • Tier 2 evidence: required for publication

  • Tier 3 evidence: required for publication

Each task attempt ran in its own isolated sandbox pod.

Tier 1 LLM Provenance

SkillSpector provider, model, analyzer revision, and determinism evidence retained for this scan.

SkillProviderAdapterAnalyzerModelRevisionDeterminism
doca-perftestnv_inferenceopenaimcp_tool_poisoningaws/anthropic/bedrock-claude-opus-5-52.13.1nondeterministic / provider_defaults
doca-perftestnv_inferenceopenaisemantic_developer_intentaws/anthropic/bedrock-claude-opus-5-52.13.1nondeterministic / provider_defaults
doca-perftestnv_inferenceopenaisemantic_quality_policyaws/anthropic/bedrock-claude-opus-5-52.13.1nondeterministic / provider_defaults
doca-perftestnv_inferenceopenaisemantic_security_discoveryaws/anthropic/bedrock-claude-opus-5-52.13.1nondeterministic / provider_defaults
doca-perftestnv_inferenceopenaimeta_analyzeraws/anthropic/bedrock-claude-opus-5-52.13.1nondeterministic / provider_defaults
  • Controls for doca-perftest: temperature=not set (source=provider_default, forwarded=no); seed=not set (source=unset, forwarded=no); reasoning_effort=not set (source=provider_default, forwarded=no)

What This Report Answers

The three-tier evaluation checks whether the skill:

  • is safe to use;

  • produces correct answers;

  • is discovered and activated when needed;

  • helps the agent complete the user's goal and expected workflow; and

  • avoids wasted skill and tool usage.

Results at a Glance

MeasureClaude Code (Baseline → Skill Uplift)Codex (Baseline → Skill Uplift)
Overall88.3% — baseline ran, but no comparable score was available; uplift unavailable78.7% — baseline ran, but no comparable score was available; uplift unavailable
Security100.0% → 100.0% (±0.0 points)100.0% → 100.0% (±0.0 points)
Correctness52.0% → 96.0% (+44.0 points)60.0% → 88.0% (+28.0 points)
Discoverability85.0% — baseline ran, but no comparable score was available; uplift unavailable81.3% — baseline ran, but no comparable score was available; uplift unavailable
Effectiveness30.0% → 65.0% (+35.0 points)35.0% → 65.0% (+30.0 points)
Efficiency95.5% — baseline ran, but no comparable score was available; uplift unavailable59.2% — baseline ran, but no comparable score was available; uplift unavailable

How to read this table: baseline is the same task attempted without the target skill. Scores are rounded to one decimal; threshold-adjacent values use additional precision so their displayed band matches the verdict. Uplift is derived from those displayed scores and shown in percentage points.

Example: 47.0% → 92.0% (+45.0 points) means the skill-assisted run scored 92.0%, 45.0 percentage points above its 47.0% no-skill baseline.

A partial dimension was calculated from only the available configured signals; review the detailed report before relying on it.

Comparison details

Shared-source comparisons use the same signals and weights on both conditions. They do not replace the full dimension scores above or change the publication verdict.

AgentDimensionBasisBaseline → With skill (uplift)Explanation
claude-codeDiscoverabilityDimension comparisonN/ADiscoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
claude-codeEfficiencyToken-only comparison98.1% → 97.2% (-0.9 points)Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.
codexDiscoverabilityDimension comparisonN/ADiscoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
codexEfficiencyToken-only comparison84.5% → 85.9% (+1.4 points)Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.

Token Usage

Actual Tier 3 execution usage is reported for every observed agent/case pair and both conditions.

AgentDataset caseWith skillWithout skillDeltaChangeCoverage
claude-codeAll cases598,414402,074+196,340+48.83%skill 5/5; base 5/5
claude-codedoca-perftest.explicit-positive.v1113,76136,385+77,376+212.66%skill 1/1; base 1/1
claude-codedoca-perftest.implicit-positive.v1149,52339,015+110,508+283.24%skill 1/1; base 1/1
claude-codedoca-perftest.implicit-positive.v2189,24771,892+117,355+163.24%skill 1/1; base 1/1
claude-codedoca-perftest.negative.v136,96336,614+349+0.95%skill 1/1; base 1/1
claude-codedoca-perftest.negative.v2108,920218,168-109,248-50.08%skill 1/1; base 1/1
codexAll cases249,551224,244+25,307+11.29%skill 5/5; base 5/5
codexdoca-perftest.explicit-positive.v162,66956,580+6,089+10.76%skill 1/1; base 1/1
codexdoca-perftest.implicit-positive.v162,68236,627+26,055+71.14%skill 1/1; base 1/1
codexdoca-perftest.implicit-positive.v254,24536,016+18,229+50.61%skill 1/1; base 1/1
codexdoca-perftest.negative.v143,57147,606-4,035-8.48%skill 1/1; base 1/1
codexdoca-perftest.negative.v226,38447,415-21,031-44.36%skill 1/1; base 1/1
ALL AGENTSDataset aggregate847,965626,318+221,647+35.39%skill 10/10; base 10/10

Prompt tokens include cached reads, so total tokens are prompt + completion (cached is not added twice). The Efficiency score uses (prompt - cached) + completion. Change is 100 * (with - without) / without; negative means fewer tokens. N/A comparisons include their reason in the coverage column; coverage is never estimated.

Tier Status

TierPurposeStatusEvidence
Tier 1Static validationPASSED WITH OBSERVATIONS11 validator(s); 13 finding(s)
Tier 2Semantic deduplicationPASSED WITH OBSERVATIONS2 validator(s); 2 finding(s)
Tier 3Live agent evaluationPASS2 agent(s); 5 task(s)

Findings and Observations

<details> <summary>Show detailed findings and successful checks</summary>

  • HIGH DUPLICATE/duplicate: Duplicate content found across CAPABILITIES.md and TASKS.md: "## Drivers" in CAPABILITIES.md (lines 23-29) vs "## select-driver" in TASKS.md (lines 31-37) (CAPABILITIES.md:23)

  • HIGH DUPLICATE/duplicate: Duplicate content found within SKILL.md: "## Examples" in SKILL.md (lines 22-27) vs "## Example questions this skill answers well" in SKILL.md (lines 36-41) (SKILL.md:22)

  • MEDIUM QUALITY/quality_discoverability: Description uses first/second person (skills/tools/doca-perftest/SKILL.md)

  • MEDIUM SCHEMA/metadata_key_style: Metadata key 'doca_version' is not kebab-case (skills/tools/doca-perftest/SKILL.md)

  • MEDIUM SCHEMA/folder_hierarchy: Unexpected nesting depth for general skill (skills/tools/doca-perftest)

  • 10 additional finding(s) are available in the full evaluation artifacts.

</details>

Scoring Methodology

<details> <summary>Show dimension definitions, source signals, and thresholds</summary>

DimensionQuestionScored signals
SecurityIs it safe to use?security (100%)
CorrectnessIs the answer correct?accuracy (100%)
DiscoverabilityWas the right skill loaded when needed?skill_execution (100%)
EffectivenessDid the skill help complete the task?goal_accuracy (50%) + behavior_check (50%)
EfficiencyDid it avoid wasted tool calls and token usage?skill_efficiency (50%) + token_efficiency (50%)
  • Dimension bands: PASS at 50% or above; NEUTRAL from 40% to below 50%; FAIL below 40%.

  • Overall Tier 3 lift: PASS at +5 points or more; FAIL at -10 points or less; values between those bands are NEUTRAL.

  • Overall verdict: PASS only when every configured dimension passes for at least one supported agent. Lift is reported as diagnostic evidence and does not override this gate.

  • The 50% attempt pass threshold is a separate per-task gate; it is not the dimension pass threshold.

  • Effectiveness is the equal-weight mean of goal completion (goal_accuracy) and expected workflow adherence (behavior_check).

  • Efficiency is 50% tool-call productivity (the backward-compatible skill_efficiency wire id) and 50% token_efficiency. Positive-case skill routing is scored under Discoverability, not Efficiency; a negative case without a routing target is N/A. N/A sources are omitted, remaining weights are renormalized, and the dimension is marked partial.

Signals present in this run:

  • security (Security): unsafe operations, secret leakage, and unauthorized access.

  • skill_execution (Skill Execution): whether the expected skill was selected, decoys were avoided, and the workflow executed.

  • skill_efficiency (Tool Productivity): tool-call productivity (legacy wire id; routing is scored under Discoverability).

  • accuracy (Accuracy): final-answer correctness against the reference answer.

  • goal_accuracy (Goal Accuracy): whether the user's goal was achieved.

  • behavior_check (Behavior Check): whether the expected workflow behavior was followed.

  • token_efficiency (Token Efficiency): actual uncached prompt plus completion usage (50% of Efficiency).

</details>

Freshness

Regenerate this benchmark when the skill, evaluation dataset, target agent/model, evaluator version, environment, or scoring policy changes.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

The author says: Requires DOCA 3.5 or later on Linux with a ConnectX or BlueField RDMA device, libibverbs (DOCA-OFED or upstream rdma-core), and OpenMPI for multi-node modes. The DOCA Verbs backend needs the doca-verbs package; the GPUNetIO engine needs doca-gpunetio, CUDA and a Volta+ GPU. Run benchmarks only on a trusted, non-shared fabric.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
NVIDIA
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/doca-perftest · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download doca-perftest.zip