Amazon just changed EC2 pricing to bill per second https://aws.amazon.com/ec2/pricing/. You’re load testing and trying to keep your costs low. What does this Amazon change mean for you? Let’s see how you can save more with Redline13 Load Testing.
Server Shutdown Setting
Redline13 has added a new setting for users to take advantage of AWS per second billing. Now instead of leaving servers running for an hour, we let you choose how long they should run. That means you can save even more by load testing with Redline13. And Redline13 was already the least expensive way to load test.
On the AWS Keys page, find the column for “Shutdown Policy”. That specifies how long after a test that servers should remain running. You can set that as low as 5 minutes.
As the screenshot says, remember that if you are running multiple tests in a row, it might be better to leave them running. It may be more economical to leave servers running if you expect to run multiple tests fairly close together. When a server starts up, there is some time taken for the server to boot and all the packages to be installed. When servers are re-used that setup time is much shorter. You have options to save more with Redline13 load testing.
RedLine13’s open architecture provides an easy, accessible, and cheap means for load testing. Precisely tune and control your cloud load agents for any given requirement, and then easily scale and repeatedly test with little effort.
Write Open Load Tests in your language. Load Tests can be written in PHP, Node.JS, or Python using your own libraries and supporting packages.
Besides the Shutdown Policy setting, there isn’t anything different you need to do. As a side note, you can shut down a server via the Server Management page and you can also shut it down via the AWS console. We know that organizations that load test are under pressure to load test more for less cost. We believe load testing shouldn’t be expensive so you can do those important tests.
Until next time, always be load testing.