We’re always collecting feedback and we take it very seriously. One common thing we hear from our users is the confusion of how our existing test types are named and work. We’ll admit our naming flat out stinks, and more importantly we assumed everyone would know exactly what the load test is doing when it runs. Clearly not everyone can have the same insights in to our service as we do, and we need to be better at providing these insights. We’re happy to let you know we’ve made things much more clear, as well as introduced a brand new testing option.
First, we changed the name of our two existing load test types to make them more closely reflect the work they’re doing when they run. Our changes include renaming Non-Cycling to Clients per test and Cycling to Maintain client load.
Then we added a new test type titled Clients per second. Below is a bit more information about how these tests types work.
Clients per test
This test allows you to specify a total number of clients to connect to your service, and then be done. When creating this test, you specify just one number, and that many clients will connect over the duration of the test. For example, if you create a 20-second test with 20,000 clients, loader will attempt to run 1,000 clients per second.
Maintain client load
If you really want to hammer your website or API (be careful), this test is the way to do it. Loader ensures that a constant number of clients is loading your service at all times. So this test makes as many requests as it can for the amount of time you specify.
This test allows you to specify a from and a to value for clients. As an example, if you specify zero and 10,000 here, the test will start with 0 clients and increase up to 10,000 simultaneous clients by the end of the test.
Clients per second
This test allows you to specify a number of clients to connect each second. When creating this test, you specify just one number, and that many clients will connect per second for the duration of the test. For example, if you create a 20-second test with 1,000 clients per second, loader will attempt to connect 20,000 clients during the test.
Check it out and keep your feedback coming. Also, check out our docs if you haven’t lately.