Application Performance Optimization

How do you identify and resolve performance bottlenecks in a production application?

SREintermediate

// interview question

How do you identify and resolve performance bottlenecks in a production application?

Sample answer

Performance optimization process: 1) Measure first - use APM tools (Datadog, New Relic) to identify slow endpoints. 2) Profile - CPU profiling, memory analysis, database query analysis. 3) Common bottlenecks: N+1 queries, missing indexes, synchronous operations that should be async, memory leaks, inefficient algorithms. 4) Load test to find breaking points. 5) Optimize incrementally - cache frequently accessed data, optimize database queries, implement connection pooling, use CDNs for static assets. Always measure impact of changes.

Why this matters

Premature optimization is the root of all evil, but measured optimization is essential. Start with observability - you can't improve what you can't measure. APM tools show where time is spent. Database queries are often the bottleneck. Caching (Redis, CDN) can dramatically improve performance but adds complexity. Load testing reveals how the system behaves under stress.

Code examples

Database query analysis

bash

# PostgreSQL slow query log
# In postgresql.conf:
# log_min_duration_statement = 1000  # Log queries > 1s

# Analyze query plan
EXPLAIN ANALYZE SELECT * FROM orders 
  WHERE user_id = 123 
  ORDER BY created_at DESC
  LIMIT 10;

# Find missing indexes
SELECT schemaname, tablename, 
       seq_scan, seq_tup_read,
       idx_scan, idx_tup_fetch
FROM pg_stat_user_tables
WHERE seq_scan > idx_scan
ORDER BY seq_tup_read DESC;

Redis caching pattern

yaml

# Kubernetes Redis deployment for caching
apiVersion: apps/v1
kind: Deployment
metadata:
  name: redis-cache
spec:
  replicas: 1
  selector:
    matchLabels:
      app: redis
  template:
    spec:
      containers:
      - name: redis
        image: redis:7-alpine
        command: ["redis-server"]
        args:
        - "--maxmemory"
        - "256mb"
        - "--maxmemory-policy"
        - "allkeys-lru"  # Evict least recently used
        resources:
          limits:
            memory: 300Mi

Common mistakes to avoid

Optimizing without measuring - guessing where bottlenecks are
Caching everything without considering cache invalidation complexity
Fixing symptoms (adding more servers) instead of root causes

Likely follow-ups

When should you use caching vs. optimizing the underlying operation?
How do you prevent cache stampede problems?
What tools do you use for load testing?

Answer out loud first, then check yourself against the model answer.

Practice all Mid-Level questions More SRE questions

#performance#optimization#apm#sre#caching

Also worth your time on this topic

Interview

Capacity Planning and Scaling

How do you approach capacity planning for a growing production system? What metrics and strategies do you use?

senior

Article

Docker Build Cache on Ephemeral CI Runners: inline, registry and local, Measured

A fresh CI runner starts with no BuildKit cache. We rebuilt a real multi-stage Node service on a new builder every time, with no cache, inline, registry min and max, and a local cache directory, and measured cold builds, a one-line change, a dependency bump, the export cost and the cache size.

Exercise

Redis Caching Strategies for Scalable Applications

Implement production-ready caching patterns with Redis to dramatically improve application performance and scalability.

70 minutes

Application Performance Optimization

More SRE interview questions

Also worth your time on this topic

Capacity Planning and Scaling

Docker Build Cache on Ephemeral CI Runners: inline, registry and local, Measured

Redis Caching Strategies for Scalable Applications