github-copilot-instructions performance-optimization.instructions.md

Performance Optimization Best Practices

Introduction

Performance isn't just a buzzword—it's the difference between a product people love and one they abandon. I've seen firsthand how a slow app can frustrate users, rack up cloud bills, and even lose customers. This guide is a living collection of the most effective, real-world performance practices I've used and reviewed, covering frontend, backend, and database layers, as well as advanced topics. Use it as a reference, a checklist, and a source of inspiration for building fast, efficient, and scalable software.

General Principles

• Measure First, Optimize Second: Always profile and measure before optimizing. Use benchmarks, profilers, and monitoring tools to identify real bottlenecks. Guessing is the enemy of performance.
  • Pro Tip: Use tools like Chrome DevTools, Lighthouse, New Relic, Datadog, Py-Spy, or your language's built-in profilers.
• Optimize for the Common Case: Focus on optimizing code paths that are most frequently executed. Don't waste time on rare edge cases unless they're critical.
• Avoid Premature Optimization: Write clear, maintainable code first; optimize only when necessary. Premature optimization can make code harder to read and maintain.
• Minimize Resource Usage: Use memory, CPU, network, and disk resources efficiently. Always ask: "Can this be done with less?"
• Prefer Simplicity: Simple algorithms and data structures are often faster and easier to optimize. Don't over-engineer.
• Document Performance Assumptions: Clearly comment on any code that is performance-critical or has non-obvious optimizations. Future maintainers (including you) will thank you.
• Understand the Platform: Know the performance characteristics of your language, framework, and runtime. What's fast in Python may be slow in JavaScript, and vice versa.
• Automate Performance Testing: Integrate performance tests and benchmarks into your CI/CD pipeline. Catch regressions early.
• Set Performance Budgets: Define acceptable limits for load time, memory usage, API latency, etc. Enforce them with automated checks.