Skip to content
Home » Case Studies » DebugBear Tests and Server Impacts

DebugBear Tests and Server Impacts

Introduction

We’ve setup 12 pages of the testing site on DebugBear to see the impact of the tests.

Results

  • 141 requests between 6am and 7am.
  • 1.95MB of bandwidth used.

In comparison

Safestyle’s site on a normal hour do

  • ~20k requests
  • ~350MB of bandwidth used.

Conclusion

Some servers (especially on shared spaces) are very bad at handling a sudden rise of requests but most server should not be impacted by DebugBear tests.

What to do if the server is impacted

  • If the server is impacted then we need to optimise its load balancing possibly using a CDN or changing the server configuration.
  • The best thing we can do on your side is spread the tests on 24h to balance the requests to the server.