Distributed load testing from DigitalOcean?

  • Posted on November 26, 2014
  • camwAsked by camw

In the Policy FAQ, it indicates that you don’t allow ddos traffic to exit your network. Is that an automated control? If I wanted to build a distributed load testing cluster on DigitalOcean would I be able to? Or would it be blocked?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Most 3rd party load testing tools I’ve come across use AWS, Google Cloud Platform , or Rackspace for their traffic gen - pay for the VM on a per minute or per hour model, and for the VU traffic (ie: LoadView which uses AWS, Google & Rackspace; or LoadNinja which uses AWS). I have yet to see a use case with a smaller player like DO. I’d be curious to see this in action, however!

@SanjuBurkule - do you have a website for TestNow? I searched but couldn’t find anything. Curious to read some documentation to learn more.

Disclaimer: We sell TestNow.

We created a load testing tool called TestNow on Digitial Ocean. TestNow creates 100s of small machines with a different browser in each machine. The machines we have created using normal username/pwd were compromised by some attacker. Hence DO had stopped us. So we created machines using ssh keys. We also used fail2ban. Our platform installs some testing tools and test sets on each of these newly created machines based on the components running on them, etc. gather reports from each of these components and different browser versions, consolidate those reports, and if all tests have passed, we destroy all these machines (to keep costs low). Takes us around 1 hour to create 100 small machines. All our load does not get distributed in parallel by DO to create servers within 55 seconds.

Hope this helps. Sanju

We’d also like to know this. If DO staff could respond, that’d be great :)