Load test reports answer two main questions: how much load did the system handle, and where did it start to degrade? Requests per second (RPS) shows throughput; latency (e.g. p95, p99) and error rate show at what point user experience or stability suffer.
When RPS is ramped up, watch for the inflection point: where latency jumps or errors appear. That often indicates a bottleneck (application, database, or network). Compare multiple runs (e.g. before and after a code or config change) to see if that point moved in the right direction.
LoadEng reports provide task-level and aggregate metrics. Use them to see which URLs or methods are slow or failing, and to set baseline targets for future releases. Pair with Engarde DDoS tests to distinguish capacity limits from attack-handling limits.
Define acceptable thresholds (e.g. p95 latency under X ms, error rate under Y%) for your SLA, and run LoadEng scenarios regularly so you notice regressions early. Documentation and training pages cover scenario design and report fields in detail.
For detailed steps, see our documentation and training center pages. Documentation · Training. For product-level details, see Engarde DDoS and LoadEng.