performance-oracle

To find performance bottlenecks, analyze source code, profiling data, and query patterns to detect algorithmic inefficiencies, N+1 queries, and memory leaks. You can fix them by applying algorithmic optimizations, adding database indexes, implementing caching layers, and reducing API round trips.

Diagnose slow database queries by examining execution plans and query patterns to detect N+1 queries and missing indexes. Fix them by adding indexes, using eager loading, and applying query optimizations to improve database performance and scalability.

Memory leaks and caching inefficiencies are caused by unbounded data structures and expensive repeated computations. Optimize caching by finding unbounded structures, memoizing expensive computations, and recommending appropriate cache layers with proper invalidation strategies.

Optimize frontend rendering by reducing API round trips, suggesting request batching, and trimming payload sizes. You can also improve frontend delivery by advising on bundle size reduction and implementing lazy loading for network and frontend optimization.

Yes, you can analyze algorithmic complexity by determining time and space complexity, flagging quadratic or worse patterns, and projecting behavior at 10x to 1000x data volumes. This helps identify scalability concerns before they impact application performance.

The best way to optimize a slow API endpoint is to analyze code paths, database interactions, and memory usage to return a prioritized list of performance issues. Apply targeted code and schema changes with benchmarking guidance to improve responsiveness.