← All Prompt Categories

📚 LLM HUB · 4 PROMPTS

Performance Engineering Best Practices

4 copy-ready AI prompts for performance engineering best practices in JMeter, k6, and Gatling. Part of the JMeter.AI LLM Hub.

Performance Testing Checklist

Generate a comprehensive performance testing checklist covering all phases:

Phase 1: Pre-Test
- [ ] Test plan reviewed and approved
- [ ] [Continue generating all checklist items]

Phase 2: Environment Setup
Phase 3: Test Data Preparation
Phase 4: Script Review
Phase 5: Test Execution
Phase 6: Monitoring Setup
Phase 7: Results Analysis
Phase 8: Reporting
Phase 9: Post-Test Cleanup

Output as a detailed, actionable Markdown checklist.

Common Performance Anti-Patterns

List the top 20 performance testing anti-patterns that engineers make with JMeter / k6, covering:

For each anti-pattern:
- Anti-pattern name
- What the engineer does wrong
- Why it leads to misleading results
- The correct approach
- Example (before/after configuration or code)

Categories to cover:
- Script design mistakes
- Load profile mistakes
- Assertion mistakes
- Environment mistakes
- Analysis mistakes
- Reporting mistakes

Performance Testing Maturity Assessment

Assess the performance testing maturity of my team based on the following current state:
[Describe: when do you test, what tools, how automated, what metrics you track, how results are used]

Use the following maturity levels:
- Level 1: Reactive (test only when problems occur)
- Level 2: Defined (some process, occasional testing)
- Level 3: Managed (regular testing, CI/CD integration)
- Level 4: Optimized (continuous performance engineering, production feedback loop)

Provide:
- Current maturity level with justification
- Gap analysis for the next level
- A 90-day roadmap to reach Level [N+1]
- Quick wins achievable in the first 30 days

Performance KPIs Dashboard Design

Design a performance engineering KPIs dashboard for a development team.

The dashboard should track:
- Per-release performance trends (response time, throughput, error rate)
- SLA compliance rate over time
- Number of performance bugs found and fixed per sprint
- Test coverage (% of critical user journeys tested)
- Time to detect performance regressions

Provide:
- Dashboard layout description
- Data sources for each KPI
- How to instrument CI/CD to auto-populate metrics
- Recommended tooling: Grafana / Datadog / Confluence
- Alert conditions for each KPI