sre-agent-isucon13

MCP tool reference — exec, benchmark_start, benchmark_status, note_write, etc. Use when: executing commands on VMs, running benchmarks, or recording findings

ISUCON13 contest manual — server topology, service management, benchmark execution, and rules. Use when: checking environment setup, running benchmarks, or understanding contest constraints

ISUPipe application manual — features, terms, constraints, and API specs. Use when: understanding the app domain, checking API behavior or MUST/MAY requirements

General strategy for identifying and adding missing database indexes in ISUCON web applications

General techniques for optimizing user icon/avatar image serving in ISUCON web applications

General techniques for identifying and fixing N+1 query problems in ISUCON web applications

Install and use alp (Access Log Profiler) to identify slow nginx endpoints and analyze request patterns

Tune Go database/sql connection pool settings for optimal MySQL performance under ISUCON load

Implement application-level in-memory caching in Go using sync.Map for frequently accessed data that rarely changes

Optimize PowerDNS performance for ISUCON competitions where DNS resolution is a component

Common ISUCON scoring patterns and strategies to achieve score jumps based on historical competition data

Tune MySQL InnoDB buffer pool and query settings for ISUCON workloads

Tune nginx worker processes, connection handling, keepalive, and logging for ISUCON workloads

Enable MySQL slow query log and use pt-query-digest to identify the most expensive database queries

Emergency rollback procedures when changes break the ISUPIPE application or benchmark fails

First 30 minutes strategy checklist for ISUCON competitions — what to do immediately after the contest starts

Configure nginx as a load balancer distributing traffic across multiple Go app workers

Distribute ISUPIPE components across 3 contest VMs for optimal resource utilization — DB on vm1, App workers on vm2/vm3