benchmarking

Run structured cronometro benchmarks for Jazz packages with worker-thread isolation.

154|13|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/garden-co/jazz --skill benchmarking-garden-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmarking
Source: https://github.com/garden-co/jazz/tree/main/.cursor/skills/benchmarking
Command: npx skills add https://github.com/garden-co/jazz --skill benchmarking-garden-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmarks for Jazz packages can be ad-hoc and hard to compare consistently. This skill provides a structured approach to writing and executing performance benchmarks, including setup, isolation, and result comparison using cronometro.

Core Features & Use Cases

  • Structured benchmarking workflow: standardizes how to measure performance across implementations.
  • Isolated execution with worker threads: ensures measurement consistency and minimizes interference.
  • Comprehensive guidance for common patterns (setup, multiple iterations, reporting, and comparing against @latest or workspace).

Quick Start

Create a bench file that benchmarks a single operation with cronometro and execute it from the bench directory using node --experimental-strip-types --no-warnings.

Frequently Asked Questions about benchmarking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run performance benchmarks for Jazz packages using cronometro?

To run performance benchmarks for Jazz packages, create a bench file with a single cronometro() call per operation and execute it from the bench directory using node --experimental-strip-types --no-warnings to measure performance consistently.

What is the best way to detect performance regressions in Node.js worker threads?

Detecting performance regressions in Node.js worker threads requires isolated execution with cronometro to minimize interference, ensuring measurement consistency when comparing @latest versus @workspace package implementations.

How do I structure a benchmarking workflow to compare @latest and workspace implementations?

Structuring a benchmarking workflow to compare implementations requires placing benchmark files under bench/jazz-tools, generating setup data, and using cronometro to produce consistent reports for @latest vs @workspace comparisons.

Does cronometro support worker-thread isolation for benchmark measurement?

Yes, cronometro supports worker-thread isolation for benchmark measurement, which ensures measurement consistency and minimizes interference when running structured performance benchmarks for Jazz packages.

Why are my ad-hoc performance benchmarks hard to compare consistently?

Ad-hoc performance benchmarks are hard to compare consistently because they lack a structured approach to setup, isolation, and result comparison, which cronometro standardizes through worker-thread execution and consistent reporting.

What do I need to set up before running cronometro benchmarks for Jazz packages?

Before running cronometro benchmarks for Jazz packages, you need cronometro installed and a bench/ directory created with a single cronometro() call per operation, typically placed under bench/jazz-tools.