perf-tuning-cycle

Automate performance testing by orchestrating an end-to-end tuning loop that runs k6 load tests, captures Prometheus metrics, analyzes bottlenecks, and generates actionable reports to prove improvements.

Measuring performance improvements end-to-end involves running smoke and load tests, capturing metrics, and using standardized diagnosis and report templates to compare before and after states for traceable results.

Set up a performance tuning cycle by applying code changes and running an automated workflow that uses k6 scripts for testing and Grafana for monitoring to capture metrics and produce analysis reports.

Yes, you can use this performance tuning workflow to conduct A/B comparisons that quantify the impact of changes by comparing before and after states to prove and document measurable improvements.

Yes, Prometheus instrumentation is required to satisfy data capture requirements, enabling the workflow to gather the metrics needed for bottleneck analysis and actionable reporting.

Diagnosing bottlenecks with automated reports relies on properly configured k6 load tests and Prometheus instrumentation; without accurate metric capture, the analysis guide and diagnosis template cannot pinpoint performance issues effectively.