Skip to content

Nvshmem collect performance data vs Nvshmem troubleshoot and report bugs

Nvshmem collect performance data is an open-source agent skill for developer tools. Nvshmem troubleshoot and report bugs is an open-source agent skill for developer tools.

  • Nvshmem collect performance data is best for run the default nvshmem put and get sanity suite on an allocated node.
  • Nvshmem troubleshoot and report bugs is best for diagnose why an nvshmem job hangs during initialization.
What it is
Nvshmem collect performance data is an open-source agent skill for developer tools.
Nvshmem troubleshoot and report bugs is an open-source agent skill for developer tools.
Best for
Run the default NVSHMEM put and get sanity suite on an allocated node
Diagnose why an NVSHMEM job hangs during initialization
Kind
Skill
Skill
Pricing
Open source
Open source
Platforms
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
GitHub stars
4K
4K
Last commit
Nov 2026
Nov 2026
License
Apache-2.0
Apache-2.0
Open source
Good for
Run the default NVSHMEM put and get sanity suite on an allocated node; Collect NVSHMEM performance evidence for a two-node placement; Package benchmark output and topology details into a shareable report
Diagnose why an NVSHMEM job hangs during initialization; Work out whether a crash is an NVSHMEM defect or a launcher problem; Check whether a known NVSHMEM issue matches my error log

What Nvshmem collect performance data does

  • Recommended device sanity suite

    Runs the four device put and get bandwidth and latency tests with two PEs as a default check.

  • Launcher and placement preflight

    Confirms ranks land on the intended hostnames and GPUs before any measured test runs.

  • Initialization probe

    Performs a minimal device-side run to confirm which NVSHMEM transport paths initialize.

  • Read-only environment collector

    Bash script that records NVSHMEM, GPU, NIC, and topology evidence from each compute node.

  • Result validation

    Checks exit status, placement, units, and numeric values before results are reported.

  • Portable handoff report

    Produces a Markdown report with commands, exit statuses, result curves, and relative artifact paths.

What Nvshmem troubleshoot and report bugs does

  • Evidence collection workflow

    Requires the exact launch command and complete per-process output before analysis begins.

  • Debug logging gate

    Asks for NVSHMEM INFO-level logs before diagnosing in-process failures, with a narrow pre-start exception.

  • Knowledge-base matching

    Matches log signatures against a bundled set of known NVSHMEM issues and reports confidence levels.

  • Version applicability checks

    Verifies version-sensitive claims and upgrade candidates against official NVSHMEM documentation.

  • Bug report drafting

    Produces paste-ready Markdown reports that mirror the NVSHMEM GitHub issue form.

  • Read-only execution boundary

    Keeps diagnosis to read-only inspection and requires explicit confirmation before any state-changing action.

Nvshmem collect performance data vs Nvshmem troubleshoot and report bugs: questions

Is Nvshmem collect performance data or Nvshmem troubleshoot and report bugs cheaper?

Both are open source. Compare current plans on each official site.

What is the difference between Nvshmem collect performance data and Nvshmem troubleshoot and report bugs?

Nvshmem collect performance data is an open-source agent skill for developer tools. Nvshmem troubleshoot and report bugs is an open-source agent skill for developer tools.

Keep comparing