mcpbeat

Cloudflare Workers Performance

secondsky/cloudflare-workers-performance

Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.

This is a copy. The original lives at comeonoliver/cloudflare-workers-performance.

28k tokens
context cost
the whole folder, loaded on every use
11
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
202
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/secondsky/claude-skills --skill cloudflare-workers-performance

The instruction itself

16 sections, as written by the author

Cloudflare Workers Performance Optimization

Techniques for maximizing Worker performance and minimizing latency.

Quick Wins

// 1. Avoid unnecessary cloning
// ❌ Bad: Clones entire request
const body = await request.clone().json();

// ✅ Good: Parse directly when not re-using body
const body = await request.json();

// 2. Use streaming instead of buffering
// ❌ Bad: Buffers entire response
const text = await response.text();
return new Response(transform(text));

// ✅ Good: Stream transformation
return new Response(response.body.pipeThrough(new TransformStream({
  transform(chunk, controller) {
    controller.enqueue(process(chunk));
  }
})));

// 3. Cache expensive operations
const cache = caches.default;
const cached = await cache.match(request);
if (cached) return cached;

Critical Rules

  • Stay under CPU limits - 10ms (free), 30ms (paid), 50ms (unbound)
  • Minimize cold starts - Keep bundles < 1MB, avoid dynamic imports
  • Use Cache API - Cache responses at the edge
  • Stream large payloads - Don't buffer entire responses
  • Batch operations - Combine multiple KV/D1 calls

Top 10 Performance Errors

| Error | Symptom | Fix |

|-------|---------|-----|

| CPU limit exceeded | Worker terminated | Optimize hot paths, use streaming |

| Cold start latency | First request slow | Reduce bundle size, avoid top-level await |

| Memory pressure | Slow GC, timeouts | Stream data, avoid large arrays |

| KV latency | Slow reads | Use Cache API, batch reads |

| D1 slow queries | High latency | Add indexes, optimize SQL |

| Large bundles | Slow cold starts | Tree-shake, code split |

| Blocking operations | Request timeouts | Use Promise.all, streaming |

| Unnecessary cloning | Memory spike | Only clone when needed |

| Missing cache | Repeated computation | Implement caching layer |

| Sync operations | CPU spikes | Use async alternatives |

CPU Optimization

Profile Hot Paths

async function profiledHandler(request: Request): Promise<Response> {
  const timing: Record<string, number> = {};

  const time = async <T>(name: string, fn: () => Promise<T>): Promise<T> => {
    const start = Date.now();
    const result = await fn();
    timing[name] = Date.now() - start;
    return result;
  };

  const data = await time('fetch', () => fetchData());
  const processed = await time('process', () => processData(data));
  const response = await time('serialize', () => serialize(processed));

  console.log('Timing:', timing);
  return new Response(response);
}

Optimize JSON Operations

// For large JSON, use streaming parser
import { JSONParser } from '@streamparser/json';

async function parseStreamingJSON(stream: ReadableStream): Promise<unknown[]> {
  const parser = new JSONParser();
  const results: unknown[] = [];

  parser.onValue = (value) => results.push(value);

  for await (const chunk of stream) {
    parser.write(chunk);
  }

  return results;
}

Memory Optimization

Avoid Large Arrays

// ❌ Bad: Loads all into memory
const items = await db.prepare('SELECT * FROM items').all();
const processed = items.results.map(transform);

// ✅ Good: Process in batches
async function* batchProcess(db: D1Database, batchSize = 100) {
  let offset = 0;
  while (true) {
    const { results } = await db
      .prepare('SELECT * FROM items LIMIT ? OFFSET ?')
      .bind(batchSize, offset)
      .all();

    if (results.length === 0) break;

    for (const item of results) {
      yield transform(item);
    }
    offset += batchSize;
  }
}

Caching Strategies

Multi-Layer Cache

interface CacheLayer {
  get(key: string): Promise<unknown | null>;
  set(key: string, value: unknown, ttl?: number): Promise<void>;
}

// Layer 1: In-memory (request-scoped)
const memoryCache = new Map<string, unknown>();

// Layer 2: Cache API (edge-local)
const edgeCache: CacheLayer = {
  async get(key) {
    const response = await caches.default.match(new Request(`https://cache/${key}`));
    return response ? response.json() : null;
  },
  async set(key, value, ttl = 60) {
    await caches.default.put(
      new Request(`https://cache/${key}`),
      new Response(JSON.stringify(value), {
        headers: { 'Cache-Control': `max-age=${ttl}` }
      })
    );
  }
};

// Layer 3: KV (global)
// Use env.KV.get/put

Bundle Optimization

// 1. Tree-shake imports
// ❌ Bad
import * as lodash from 'lodash';

// ✅ Good
import { debounce } from 'lodash-es';

// 2. Lazy load heavy dependencies
let heavyLib: typeof import('heavy-lib') | undefined;

async function getHeavyLib() {
  if (!heavyLib) {
    heavyLib = await import('heavy-lib');
  }
  return heavyLib;
}

When to Load References

Load specific references based on the task:

  • Optimizing CPU usage? → Load references/cpu-optimization.md
  • Memory issues? → Load references/memory-optimization.md
  • Implementing caching? → Load references/caching-strategies.md
  • Reducing bundle size? → Load references/bundle-optimization.md
  • Cold start problems? → Load references/cold-starts.md

Templates

| Template | Purpose | Use When |

|----------|---------|----------|

| templates/performance-middleware.ts | Performance monitoring | Adding timing/profiling |

| templates/caching-layer.ts | Multi-layer caching | Implementing cache |

| templates/optimized-worker.ts | Performance patterns | Starting optimized worker |

Scripts

| Script | Purpose | Command |

|--------|---------|---------|

| scripts/benchmark.sh | Load testing | ./benchmark.sh <url> |

| scripts/profile-worker.sh | CPU profiling | ./profile-worker.sh |

Resources

  • Performance: https://developers.cloudflare.com/workers/platform/performance/
  • Limits: https://developers.cloudflare.com/workers/platform/limits/
  • Caching: https://developers.cloudflare.com/workers/runtime-apis/cache/

How to use it

Copy the folder

Take secondsky/cloudflare-workers-performance from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.