smithery/redisearch

run-rust-benchmarks

Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.

Installation

$ npx skills add smithery/redisearch --skill run-rust-benchmarks

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/redisearch · top by installs.

npx skills add smithery/redisearch

Browse all from smithery/redisearch

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,904 B
  • docs SUMMARY.md 96 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Rust Benchmarks Skill

Run Rust benchmarks and compare performance with the C implementation.

Arguments

  • <crate>: Run the given benchmark crate (e.g., /run-rust-benchmarks rqeiteratorsbencher)
  • <crate> <bench>: Run specific bench in a benchmark crate (e.g., /run-rust-benchmarks rqeiteratorsbencher "Iterator - InvertedIndex - Numeric - Read Dense")

Arguments provided: $ARGUMENTS

Instructions

  1. Check the arguments provided above:

- If a crate name is provided, run benchmarks for that crate: ``bash cargo bench --manifest-path src/redisearchrs/Cargo.toml -p <cratename> ` - If both crate and bench name are provided, run the specific bench: `bash cargo bench --manifest-path src/redisearchrs/Cargo.toml -p <cratename> <bench_name> ``

  1. Run benchmarks only once. If the output is too large or truncated, extract the timing data from the saved output file rather than re-running the benchmarks.
  2. Once the benchmarks are complete, generate a summary comparing the average run times between the Rust and C implementations.
  3. Ask the user: "Would you like a copyable markdown version for your PR description?" If yes, re-emit the summary table inside a fenced `markdown code block so it can be pasted directly.

Common Benchmark Commands

# Bench given crate
cargo bench --manifest-path src/redisearch_rs/Cargo.toml -p rqe_iterators_bencher
cargo bench --manifest-path src/redisearch_rs/Cargo.toml -p inverted_index_bencher

# Run a specific benchmark
cargo bench --manifest-path src/redisearch_rs/Cargo.toml -p rqe_iterators_bencher "Iterator - InvertedIndex - Numeric - Read Dense"