Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

$pwd:

run-rust-benchmarks

Name: Run Rust Benchmarks
Author: RediSearch

// 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.

Executar no Manus

$ git log --oneline --stat

stars:6.151

forks:587

updated:29 de maio de 2026 às 08:53

SKILL.md

readonly

name	run-rust-benchmarks
description	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.

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>

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 ```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"

related-skills.json

mesmo repositório

build.md

from "RediSearch/RediSearch"

Compile the project to verify changes build successfully. Use this to verify your changes build properly together with the complete project and dependencies, and make sure to use it before running end to end tests.

2026-05-296.2k

investigate-flaky-test.md

from "RediSearch/RediSearch"

Investigate a RediSearch flaky-test report from a Jira key, CI failure, test id, or local logs. Use this to collect evidence, identify a supported root cause, and propose a real fix; if the evidence is insufficient, say so and ask for the missing data instead of suggesting workaround-only fixes or skip_until.

2026-05-296.2k

jj-fix-conflicts.md

from "RediSearch/RediSearch"

Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.

2026-05-296.2k

lint.md

from "RediSearch/RediSearch"

Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.

2026-05-296.2k

port-c-module.md

from "RediSearch/RediSearch"

Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.

2026-05-296.2k

run-rust-tests.md

from "RediSearch/RediSearch"

Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.

2026-05-296.2k

package.json

"author": "RediSearch"

"repository": "RediSearch/RediSearch"

Abrir repositório GitHub Ver repositórios do creator

$ install --global

$ download --local

Executar no Manus

$ useful --forSOC

Desenvolvedores de softwareInformática e Matemática15-1252L4

name	run-rust-benchmarks
description	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.

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>

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 ```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"

run-rust-benchmarks

Rust Benchmarks Skill

Arguments

Instructions

Common Benchmark Commands

Mais deste repositório

Mais deste repositório

Rust Benchmarks Skill

Arguments

Instructions

Common Benchmark Commands