Menu
Configure nginx as a load balancer distributing traffic across multiple Go app workers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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
| name | load-balancer-setup |
| description | Configure nginx as a load balancer distributing traffic across multiple Go app workers |
Configure nginx on vm1 to distribute requests across app workers on vm2/vm3.
upstream app {
server 10.0.1.5:443; # vm2
server 10.0.1.6:443; # vm3
keepalive 64;
}
If one VM has more resources, use weights:
upstream app {
server 10.0.1.5:443 weight=3; # vm2: more powerful
server 10.0.1.6:443 weight=2; # vm3
keepalive 64;
}
exec host="vm1" command="sudo tee /etc/nginx/sites-enabled/isupipe.conf << 'NGINX'
upstream app {
server 10.0.1.5:443;
server 10.0.1.6:443;
keepalive 64;
}
server {
listen 443 ssl http2;
server_name *.u.isucon.dev;
ssl_certificate /etc/nginx/tls/_.u.isucon.dev.crt;
ssl_certificate_key /etc/nginx/tls/_.u.isucon.dev.key;
proxy_http_version 1.1;
proxy_set_header Connection \"\";
proxy_set_header Host \\$host;
proxy_set_header X-Real-IP \\$remote_addr;
proxy_set_header X-Forwarded-For \\$proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
location / {
proxy_pass https://app;
}
}
NGINX"
exec host="vm1" command="sudo nginx -t && sudo systemctl reload nginx"
Add passive health checks to remove failed backends:
upstream app {
server 10.0.1.5:443 max_fails=3 fail_timeout=10s;
server 10.0.1.6:443 max_fails=3 fail_timeout=10s;
keepalive 64;
}
If the app stores session state locally (not in MySQL), use ip_hash:
upstream app {
ip_hash;
server 10.0.1.5:443;
server 10.0.1.6:443;
}
Note: ISUPIPE stores sessions in cookies with MySQL, so sticky sessions are not required.
exec host="vm1" command="curl -sk -o /dev/null -w '%{http_code}' https://pipe.u.isucon.dev/api/tag"