go-performance-reviewer

Identify performance bottlenecks in Go applications through profiling-first analysis. Collect CPU, memory, and GC data to locate hot paths, requiring explicit profiling data and benchmarks to justify changes.

Reduce memory allocations in your Go microservice by analyzing heap escapes and tuning connection pools. Use benchmark-driven optimization to compare before and after states, confirming improvements in resource usage.

Validate Go performance optimizations using benchmark-driven analysis to compare before and after results. This evidence-based approach confirms that code changes actually improve CPU, memory, and GC behavior.

Yes, you can analyze GC behavior and connection pools in Go libraries. The analysis applies to typical Go services, libraries, and microservices where CPU, memory, and GC behavior require reduction.

You need profiling data to optimize Go code when identifying hot paths and validating changes. Explicit profiling data, benchmarks, and evidence-based recommendations are required to justify modifications to allocations and pool usage.