Swell Lifecycle and Reports
Swell Phases
Suggested:
text
Created
-> Validating
-> Preflight
-> Calibrating
-> Preparing
-> RampUp
-> Hold
-> RampDown
-> Draining
-> Collecting
-> Reporting
-> Completed
Any phase -> Failed / Cancelled / InvalidPhase boundaries must be written into the event timeline.
Report Structure
- Experiment Summary
- Spectrum / Load Profile
- Planned vs Actual Arrival
- Concurrency Curve
- Client Performance
- Generator Health
- Engine Bot Backend Details
- Server Performance (Basin)
- Correlation Analysis
- Bottleneck Analysis
- Data Quality
- Test Validity
- Environment / Version / Configuration
- Raw Data References
Constraints on Report Conclusions
- Client latency does not substitute for server-side tick metrics.
- High CPU does not automatically prove CPU is the only bottleneck.
- Correlated metric curves do not imply causation.
- When the generator is saturated, no conclusion about maximum server capacity should be given.
- When monitoring coverage is insufficient, conclusion confidence must be lowered.
- Results from different Backends should be viewable in groups.