Scraping Load Testing - Test #3

Summary

The load test involved setting up an autoscaling option and adjusting the hard and soft limits for the Fly.io configuration. The test environment consisted of 5 machines, with 3 machines automatically scaling up during the test. Despite the scaling, there were 653 timeouts (7.3%) and 2 HTTP 502 responses (0.02%). The average response time was 3037.2 ms, with a peak response time of 9941 ms. Further adjustments to the soft limit are recommended to improve performance and reduce errors.

Table of Contents

• Scraping Load Testing - Test #3
  • Summary
  • Table of Contents
  • Test environment
    • Machines
  • Load Test Phases
    • Configuration
    • Results
    • Metrics
  • Conclusions and Next Steps
    • Conclusions
    • Next Steps

Test environment

Machines

Load Test Phases

Configuration

# fly.staging.toml
[http_service.concurrency]
  type = "requests"
  hard_limit = 100
  soft_limit = 75

# load-test.yml
- duration: 60
arrivalRate: 10  # Initial load
- duration: 120
arrivalRate: 20  # Increased load
- duration: 180
arrivalRate: 30  # Peak load
- duration: 60
arrivalRate: 10  # Cool down

Results

Date: 14:53:32(-0300)

Metrics

Conclusions and Next Steps

Conclusions

1. Performance: The system handled 9000 requests with a mean response time of 3037.2 ms. There were 653 timeouts and 2 HTTP 502 responses.
2. Autoscaling: Three machines automatically scaled up during the test, but the scaling was not sufficient to prevent all errors.
3. Response Times: The peak response time was 9941 ms, indicating that the system struggled under peak load conditions.

Next Steps

1. Adjust Soft Limit: Change the soft limit to 100 and the hard limit to 50 to test if machines will start faster and reduce the number of 502 errors.
2. Further Load Tests: Conduct additional load tests with the new configuration to assess improvements.

By following these steps, we can enhance the system's performance and reliability under varying load conditions.