Skip to content
cccskills
FreePublished on GitHub

worker-benchmarks

Measure performance in the agentic-flow worker system, including trigger detection, agent selection, caching, and concurrent operations. Run a full suite or individual benchmarks to compare response times and resource usage against configured targets.

OriginalShow the original description

Run comprehensive worker system benchmarks and performance analysis

See how to install

Good for

  • Checking overall worker system performance
  • Measuring trigger detection and agent selection speed
  • Examining cache behavior and memory usage
  • Verifying concurrent worker performance against targets

Files included (1)

  • SKILL.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Worker Benchmarks Skill

Run comprehensive performance benchmarks for the agentic-flow worker system.

Quick Start

# Run full benchmark suite
npx agentic-flow workers benchmark

# Run specific benchmark
npx agentic-flow workers benchmark --type trigger-detection
npx agentic-flow workers benchmark --type registry
npx agentic-flow workers benchmark --type agent-selection
npx agentic-flow workers benchmark --type concurrent

Benchmark Types

1. Trigger Detection (trigger-detection)

Tests keyword detection speed across 12 worker triggers.

  • Target: p95 < 5ms
  • Iterations: 1000
  • Metrics: latency, throughput, histogram

2. Worker Registry (registry)

Tests CRUD operations on worker entries.

  • Target: p95 < 10ms
  • Iterations: 500 creates, gets, updates
  • Metrics: per-operation latency breakdown

3. Agent Selection (agent-selection)

Tests performance-based agent selection.

  • Target: p95 < 1ms
  • Iterations: 1000
  • Metrics: selection confidence, agent scores

4. Model Cache (cache)

Tests model caching performance.

  • Target: p95 < 0.5ms
  • Metrics: hit rate, cache size, eviction stats

5. Concurrent Workers (concurrent)

Tests parallel worker creation and updates.

  • Target: < 1000ms for 10 workers
  • Metrics: per-worker latency, memory usage

6. Memory Key Generation (memory-keys)

Tests memory pattern key generation.

  • Target: p95 < 0.1ms
  • Iterations: 5000
  • Metrics: unique patterns, throughput

Output Format

═══════════════════════════════════════════════════════════
📈 BENCHMARK RESULTS
═══════════════════════════════════════════════════════════

✅ Trigger Detection
   Operation: detect
   Count: 1,000
   Avg: 0.045ms | p95: 0.120ms (target: 5ms)
   Throughput: 22,222 ops/s
   Memory Δ: 0.12MB

✅ Worker Registry
   Operation: crud
   Count: 1,500
   Avg: 1.234ms | p95: 3.456ms (target: 10ms)
   Throughput: 810 ops/s
   Memory Δ: 2.34MB

───────────────────────────────────────────────────────────
📊 SUMMARY
───────────────────────────────────────────────────────────
Total Tests: 6
Passed: 6 | Failed: 0
Avg Latency: 0.567ms
Total Duration: 2345ms
Peak Memory: 8.90MB
═══════════════════════════════════════════════════════════

Integration with Settings

Benchmark thresholds are configured in .claude/settings.json:

{
  "performance": {
    "benchmarkThresholds": {
      "triggerDetection": { "p95Ms": 5 },
      "workerRegistry": { "p95Ms": 10 },
      "agentSelection": { "p95Ms": 1 },
      "memoryKeyGeneration": { "p95Ms": 0.1 },
      "concurrentWorkers": { "totalMs": 1000 }
    }
  }
}

Programmatic Usage

import { workerBenchmarks, runBenchmarks } from 'agentic-flow/workers/worker-benchmarks';

// Run full suite
const suite = await runBenchmarks();
console.log(suite.summary);

// Run individual benchmarks
const triggerResult = await workerBenchmarks.benchmarkTriggerDetection(1000);
const registryResult = await workerBenchmarks.benchmarkRegistryOperations(500);

Performance Optimization Tips

  1. Model Cache: Enable with CLAUDE_FLOW_MODEL_CACHE_MB=512
  2. Parallel Workers: Enable with CLAUDE_FLOW_WORKER_PARALLEL=true
  3. Warning Suppression: Enable with CLAUDE_FLOW_SUPPRESS_WARNINGS=true
  4. SQLite WAL Mode: Automatic for better concurrent performance

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-create

FreeSummary

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-index

FreeSummary

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-reindex

FreeSummary

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-review

FreeSummary

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-verify

FreeSummary

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo76.8KUpdated Oct 18, 2026

See all skills by ruvnet

Report a problem with this skill