benchmark-hotpath

Étoiles10

Forks0

Mis à jour18 juin 2026 à 16:10

Add performance benchmarks to hot-path functions that run on every state update (settings, auth, etc.) to establish baselines and catch regressions

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

OneOfOne

OneOfOne/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	benchmark-hotpath
description	Add performance benchmarks to hot-path functions that run on every state update (settings, auth, etc.) to establish baselines and catch regressions

Benchmarking Hot-Path Functions

Hot-path functions in this codebase (like diffObjects, fetch, store operations) run on every state update. Establish performance baselines with Jest benchmarks.

Procedure

Identify the function — find where it's called frequently (search for usage patterns, check state updates).
Create benchmark file — add a new describe('X benchmarks') block to the existing test file (e.g., utils/__tests__/diff.test.ts).
Design test scenarios — cover these categories:
- Primitives — same value (fast path) + different values
- Small objects — one property changed + identical (fast path)
- Nested objects — 3-level deep change (recursive nesting)
- Arrays — same length with change + different lengths (short-circuit)
- Null handling — null → object expansion + object → null expansion
Set iteration counts — choose iterations so each test completes in ~20-50ms:
- Primitives: 1M iterations (fast, no allocation)
- Small objects: 100K iterations
- Nested objects: 10K iterations
- Arrays: 100K iterations
- Null expansions: 100K iterations
Use performance.now() — measure elapsed time, assert it's under 500ms (sanity check).
Run with filter — bun jest diff --testNamePattern="benchmarks"

Example Pattern

describe('diffObjects benchmarks', () => {
  describe('primitive throughput', () => {
    it('primitives (same value)', () => {
      const a = 42;
      const b = 42;
      const iterations = 1_000_000;
      const start = performance.now();
      for (let i = 0; i < iterations; i++) {
        diffObjects(a, b);
      }
      const elapsed = performance.now() - start;
      expect(elapsed).toBeLessThan(500); // sanity: should be fast
    });
  });
});

Key Points

Fast paths matter — test both the optimized (same value) and normal case
Short-circuits matter — test cases that exit early (array length mismatch, null expansions)
Keep it fast — benchmarks should complete in <500ms total
Run selectively — use --testNamePattern="benchmarks" to run only benchmarks

Plus depuis ce dépôt

même dépôt

go-inline-budget-optimization

OneOfOne/dotfiles

Systematically reduce Go function cost below the 80-unit inlining budget for hot-path performance

2026-06-1810

sync-agents-md-with-package-json

OneOfOne/dotfiles

When updating AGENTS.md or after any dependency changes, cross-reference package.json versions against AGENTS.md to ensure accuracy

2026-06-1810

deepwork

OneOfOne/dotfiles

Orchestrator-only workflow for heavy coding sessions, multi-phase implementation, and risky refactors. Use for complex work that needs planning, review gates, and persistent progress tracking.

2026-06-1310

oh-my-opencode-slim

OneOfOne/dotfiles

Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.

2026-06-1310

Benchmarking Hot-Path Functions

Hot-path functions in this codebase (like diffObjects, fetch, store operations) run on every state update. Establish performance baselines with Jest benchmarks.

Procedure

Identify the function — find where it's called frequently (search for usage patterns, check state updates).

Create benchmark file — add a new describe('X benchmarks') block to the existing test file (e.g., utils/__tests__/diff.test.ts).

Design test scenarios — cover these categories:

Primitives — same value (fast path) + different values
Small objects — one property changed + identical (fast path)
Nested objects — 3-level deep change (recursive nesting)
Arrays — same length with change + different lengths (short-circuit)
Null handling — null → object expansion + object → null expansion

Set iteration counts — choose iterations so each test completes in ~20-50ms:

Primitives: 1M iterations (fast, no allocation)
Small objects: 100K iterations
Nested objects: 10K iterations
Arrays: 100K iterations
Null expansions: 100K iterations

Use performance.now() — measure elapsed time, assert it's under 500ms (sanity check).

Run with filter — bun jest diff --testNamePattern="benchmarks"

Example Pattern

describe('diffObjects benchmarks', () => { describe('primitive throughput', () => { it('primitives (same value)', () => { const a = 42; const b = 42; const iterations = 1_000_000; const start = performance.now(); for (let i = 0; i < iterations; i++) { diffObjects(a, b); } const elapsed = performance.now() - start; expect(elapsed).toBeLessThan(500); // sanity: should be fast }); }); });

Key Points

Fast paths matter — test both the optimized (same value) and normal case

Short-circuits matter — test cases that exit early (array length mismatch, null expansions)

Keep it fast — benchmarks should complete in <500ms total

Run selectively — use --testNamePattern="benchmarks" to run only benchmarks