run-rust-benchmarks
It runs cargo benchmarks, compares them against C implementation baselines, and creates markdown reports for pull requests.
Install
mkdir -p .claude/skills/run-rust-benchmarks && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3445" && unzip -o skill.zip -d .claude/skills/run-rust-benchmarks && rm skill.zipInstalls to .claude/skills/run-rust-benchmarks
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Execute crate-specific benchmarks
- →Run targeted individual benchmark tasks
- →Aggregate timing data for performance comparison
- →Generate markdown tables for PR documentation
How it works
Invokes `cargo bench` on specific manifest paths and formats the resulting timing data into a comparison summary.
Inputs & outputs
When to use run-rust-benchmarks
- →Compare Rust performance vs C
- →Run crate-specific benchmarks
- →Generate performance report for PR
About this skill
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 rqe_iterators_bencher)<crate> <bench>: Run specific bench in a benchmark crate (e.g.,/run-rust-benchmarks rqe_iterators_bencher "Iterator - InvertedIndex - Numeric - Read Dense")
Arguments provided: $ARGUMENTS
Instructions
- Check the arguments provided above:
- If a crate name is provided, run benchmarks for that crate:
cargo bench --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> - If both crate and bench name are provided, run the specific bench:
cargo bench --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> <bench_name>
- If a crate name is provided, run benchmarks for that crate:
- 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.
- Once the benchmarks are complete, generate a summary comparing the average run times between the Rust and C implementations.
- Ask the user: "Would you like a copyable markdown version for your PR description?" If yes, re-emit the summary table inside a fenced
```markdowncode 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"
When not to use it
- →When attempting to benchmark non-Rust components
- →When a benchmark has already been run in the same session
Prerequisites
Limitations
- →Avoids re-running benchmarks if output is available
- →Limited to predefined benchmark crates
How it compares
It automatically structures performance regression data for PRs, whereas manual benchmarking requires manual data aggregation.
Compared to similar skills
run-rust-benchmarks side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| run-rust-benchmarks (this skill) | 1 | 2mo | Review | Intermediate |
| rust-async-patterns | 11 | 2mo | Review | Intermediate |
| debug-lldb | 1 | 7mo | Review | Intermediate |
| rust-pro | 3 | 26d | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by RediSearch
View all by RediSearch →You might also like
rust-async-patterns
wshobson
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
debug-lldb
regenrek
Capture and analyze thread backtraces with LLDB/GDB to debug hangs, deadlocks, UI freezes, IPC stalls, or high-CPU loops across any language or project. Use when an app becomes unresponsive, switching contexts stalls, or you need thread stacks to locate lock inversion or blocking calls.
rust-pro
vudovn
Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
analyze-ci-speed
Sovereign-Labs
Analyze compilation time and test durations from CI logs. Use when the user asks about slow builds, slow tests, or wants to optimize CI time.
jit-overview
facet-rs
Orientation to facet-format JIT deserialization (tiering, fallbacks, key types/entry points) and where to look when changing or debugging JIT code
domain-ml
actionbook
Use when building ML/AI apps in Rust. Keywords: machine learning, ML, AI, tensor, model, inference, neural network, deep learning, training, prediction, ndarray, tch-rs, burn, candle, 机器学习, 人工智能, 模型推理