perf-benchmarker

Benchmark Cloudflare Workers latency, CPU time, and bundle size.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/cffrank/paperclip-skills-agents --skill perf-benchmarker-cffrank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-benchmarker
Source: https://github.com/cffrank/paperclip-skills-agents/tree/main/skills/perf-benchmarker
Command: npx skills add https://github.com/cffrank/paperclip-skills-agents --skill perf-benchmarker-cffrank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance benchmarking for Cloudflare Workers to identify latency, CPU time, and bundle size tracking, helping optimize runtime and deployments.

Core Features & Use Cases

  • Per-request latency measurement and CPU time accounting
  • D1 query profiling, bundle size tracking, and edge cache analysis
  • Use cases include detecting slow endpoints, validating optimizations, and regression testing across deployments

Quick Start

Run the benchmark against a deployed Worker URL to generate baseline metrics.

Frequently Asked Questions about perf-benchmarker

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

FAQPage Schema
How do I benchmark Cloudflare Workers performance for latency and CPU time?

Benchmark Cloudflare Workers performance by deploying instrumentation hooks to measure per-request latency, track CPU time accounting, and generate baseline metrics against a deployed Worker URL to identify optimization opportunities.

What is the best way to profile D1 query latency at the edge?

Profile D1 query latency by applying per-request timing and D1 query profiling instrumentation to your Cloudflare Workers, isolating slow database paths and producing actionable metrics for edge cache analysis.

Can I track bundle size regressions across Cloudflare Workers deployments?

Track bundle size regressions by running the benchmark against your deployed Worker URL to generate baseline metrics, validating optimizations and detecting deployment anomalies through continuous baseline and budget tracking.

Do I need instrumentation hooks to measure cold start latency in Workers?

Instrumentation hooks are required to measure cold start latency, capturing per-request timing data and CPU time accounting to identify slow paths and optimization opportunities within your Cloudflare Workers deployment.

How does baseline and budget tracking work for edge cache analysis?

Baseline and budget tracking records initial latency, CPU time, and bundle size metrics, then compares subsequent edge cache analysis results against these thresholds to detect slow endpoints and performance regressions.

What metrics are needed to identify slow paths in Cloudflare Workers API routes?

Identifying slow paths in API routes requires per-request latency measurement, CPU time accounting, and D1 query profiling metrics, which together pinpoint performance bottlenecks and optimization opportunities across edge deployments.