with one click
performance-efficiency
// Evaluate a workload's performance efficiency against the Well-Architected Performance Efficiency pillar, covering resource selection, scaling, monitoring, and optimization opportunities.
// Evaluate a workload's performance efficiency against the Well-Architected Performance Efficiency pillar, covering resource selection, scaling, monitoring, and optimization opportunities.
Generate a Well-Architected-aligned Architecture Decision Record (ADR) that documents a design decision with context, options evaluated, trade-offs, and WA pillar impact.
Analyze an AWS architecture for cost waste, right-sizing opportunities, and pricing model improvements aligned with the Well-Architected Cost Optimization pillar.
Assess a workload's readiness to migrate to AWS using Well-Architected principles, covering the 7 Rs, dependencies, risks, and a migration plan.
Assess a workload's operational excellence posture against the Well-Architected Operational Excellence pillar, covering organization, preparation, operation, and evolution. Use this skill when evaluating CI/CD practices, observability, incident management, runbook coverage, or operational maturity.
Identify single points of failure, assess recovery capabilities, and produce a prioritized remediation plan aligned with the Well-Architected Reliability pillar.
Deep-dive security posture assessment against the Well-Architected Security pillar, covering identity, detection, infrastructure protection, data protection, and incident response.
| name | performance-efficiency |
| description | Evaluate a workload's performance efficiency against the Well-Architected Performance Efficiency pillar, covering resource selection, scaling, monitoring, and optimization opportunities. |
| version | 1.1.0 |
Ask the user:
What workload would you like me to assess for performance efficiency? Please share:
- Architecture overview (compute, storage, database, networking services)
- Performance requirements (latency targets, throughput needs, concurrent users)
- Current baselines (p50/p95/p99 latency, request rates, error rates)
- Known bottlenecks (optional — areas you suspect are underperforming)
If context is already provided, proceed directly.
Classify findings by severity:
Assess whether optimal resource types are used:
Evaluate:
Assess:
Evaluate:
Assess:
Output:
# Performance Efficiency Assessment: {Workload Name}
## Summary
- **Date**: {date}
- **Latency target**: {target} | **Current**: {p50/p95/p99}
- **Throughput target**: {target} | **Current**: {actual}
- **Findings**: {X} Critical, {Y} High, {Z} Medium
## Performance Scorecard
| Domain | Score (1-5) | Key Gap |
|--------|-------------|---------|
| Resource Selection | {score} | {gap} |
| Scaling & Elasticity | {score} | {gap} |
| Caching | {score} | {gap} |
| Data & Network | {score} | {gap} |
| Monitoring & Optimization | {score} | {gap} |
## Critical Performance Issues
{Each: what's bottlenecked, severity, impact on user experience, recommendation, expected improvement, AWS service}
## Optimization Opportunities
### Resource Selection
| Resource | Current | Recommended | Expected Improvement | AWS Service |
|----------|---------|-------------|---------------------|-------------|
| {resource} | {current config} | {recommended} | {improvement} | {service} |
### Scaling Improvements
{Each: current limitation, recommended change, AWS service, implementation approach}
### Caching Opportunities
{Each: cache layer to add/improve, expected hit ratio, latency reduction, AWS service}
### Data and Network Optimizations
{Each: current pattern, optimized pattern, expected benefit, AWS service}
## Remediation Plan
### Quick Wins (< 1 week)
{Configuration changes, enabling features, easy right-sizing}
### Foundation (1-4 weeks)
{Caching layers, scaling policies, monitoring improvements}
### Strategic (1-3 months)
{Architecture changes, database migrations, global distribution}
## Next Steps
{Concrete actions: load test scenarios to run, metrics to instrument, experiments to try}
After delivering the assessment, offer:
Would you like me to:
- Deep-dive into a specific bottleneck?
- Design a caching strategy for a particular data flow?
- Create a load testing plan with target scenarios?
- Evaluate alternative architectures for a specific component?
- Model the performance impact of a scaling change?