Scraping Load Testing - Test #4

Summary

The load test was conducted with the Fly.io configuration set to a hard limit of 100 and a soft limit of 50. The test involved four phases with varying arrival rates. Despite the adjustments, there were 1329 timeouts (14.8%) but no HTTP 502 responses. The average response time was 3547.9 ms, with a peak response time of 9935 ms. Further adjustments to the artillery timeout configuration are recommended to improve performance.

Table of Contents

• Scraping Load Testing - Test #4
  • 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 = 50

# 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: 15:43:26(-0300)

Metrics

Conclusions and Next Steps

Conclusions

1. Performance: The system handled 9000 requests with a mean response time of 3547.9 ms. There were 1329 timeouts but no HTTP 502 responses.
2. Response Times: The peak response time was 9935 ms, indicating that the system struggled under peak load conditions.

Next Steps

1. Adjust Timeout Configuration: Change the artillery timeout configuration to reduce the number of timeouts.
2. Further Load Tests: Conduct additional load tests with the new timeout configuration to assess improvements.

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