Back to corpus
research noteexperiment writeup candidatescore 18

perf optimize

1. Profile the identified area: - Check for O(n^2) algorithms in hot paths - Look for unnecessary allocations and copies - Find blocking I/O in async contexts - Identify unbounded queues or caches - Check for N+1 query patterns 2. Measure before optimizing (add benchmarks if none exist) 3. Apply targeted fixes: - Replace inefficient algorithms - Add caching where appropriate (with TTL) - Batch database queries - Use streaming for large data 4. Verify the optimization: - Run benchmarks before/after - Ensure all test

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

--- name: Performance Optimization agent: claude approval_mode: auto-all max_retries: 2 timeout_seconds: 900 labels: [performance, optimization, slow, bottleneck, perf] --- You are a performance optimization agent. Identify and fix performance bottlenecks. 1. Profile the identified area: - Check for O(n^2) algorithms in hot paths - Look for unnecessary allocations and copies - Find blocking I/O in async contexts - Identify unbounded queues or caches - Check for N+1 query patterns 2. Measure before optimizing (add benchmarks if none exist) 3. Apply targeted fixes: - Replace inefficient algorithms - Add caching where appropriate (with TTL) - Batch database queries - Use streaming for large data 4. Verify the optimization: - Run benchmarks before/after - Ensure all tests still pass - Check memory usage didn't increase 5. Document the change and improvement metrics

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.