Automated summary
Runs performance benchmarks for the compute-average-income implementation across multiple languages (Kotlin, GraalVM, Rust, Haskell) using Gradle.
Strengths
- Multi-language support (Kotlin, GraalVM, Rust, Haskell) for performance comparison.
- Automation via Gradle for reproducible execution.
- Includes Haskell profiling for deeper analysis.
Limitations
- Requires specific environment variables (JAVA_HOME, GRAALVM_HOME).
- Depends on Gradle and JDK toolchains which can be heavy to set up.
- Limited to the 'compute-average-income' project only.
When you need to compare the performance of the same business logic implemented in different compiled languages.
For generic benchmarks or outside the context of the compute-average-income project.
Security analysis
SafeThe skill only contains environment variable setting and gradle build commands; no destructive, exfiltration, or obfuscated actions.
No concerns found
How this analysis is madeExamples
Run all compute-average-income benchmarks for Kotlin, GraalVM, Rust, and Haskell.Profile the Haskell implementation of compute-average-income.Run the Rust benchmark for compute-average-income.run-benchmarks
Use this skill when the user wants to run performance benchmarks, compare languages, or test the compute-average-income implementations.
Instructions
-
Set JAVA_HOME to Java 23 for Gradle compatibility:
export JAVA_HOME=/Users/tnfink/Library/Java/JavaVirtualMachines/openjdk-23.0.1/Contents/Home -
Run all benchmarks with:
./gradlew computeAverageIncomeOr run individual language benchmarks:
- Kotlin:
./gradlew computeAverageIncomeKotlin - GraalVM:
./gradlew computeAverageIncomeGraalVM(requires GRAALVM_HOME) - Rust:
./gradlew computeAverageIncomeRust - Haskell:
./gradlew computeAverageIncomeHaskell
- Kotlin:
-
For Haskell profiling:
./gradlew profileAverageIncomeHaskell
Notes
- Gradle 9.2.1 uses JDK 21 toolchain (auto-provisioned via foojay)
- GraalVM benchmark requires GRAALVM_HOME environment variable set
- Haskell uses GHC 9.10.3 (LTS-24.25)
- Rust uses cargo with --release flag
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/run-performance-benchmarks-mmk3ni4w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/run-performance-benchmarks-mmk3ni4w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/run-performance-benchmarks-mmk3ni4w/download' --output '.skill-downloads/run-performance-benchmarks-mmk3ni4w/SKILL.md.part' && mv '.skill-downloads/run-performance-benchmarks-mmk3ni4w/SKILL.md.part' '.skill-downloads/run-performance-benchmarks-mmk3ni4w/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/run-performance-benchmarks-mmk3ni4w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.