Running a load test

To start a test, go to Maelstrom → Run test. You’ll choose a target, configure the load, and launch — then watch live progress as virtual users ramp up.

Caution

Only run load tests against targets you own or are authorized to test. A load test deliberately drives heavy traffic at the target and can affect its availability for real users.

1. Choose a target

Pick the site you want to test. Targets are the same ones you register elsewhere in BestDefense, so a target you’ve already added for scanning is available here too.

Drive load at specific routes

If you’ve configured routes for the site, you can direct the load at specific routes rather than the whole target — useful for stress-testing a particular endpoint or user journey. Without routes, the test drives the target as a whole.

2. Configure the load

Set the parameters that shape the test:

• Virtual user count — how many simulated concurrent users to drive. This is the primary measure of how much load you apply.
• Ramp-up time — how long Maelstrom takes to reach the full virtual-user count. A gradual ramp lets you see where performance starts to degrade; an instant ramp tests a sudden surge.
• Test duration — how long the test runs once at full load.
• Load profile — the shape of the load over time, such as ramp, step, spike, or hold. Choose the profile that matches the scenario you want to validate.

Tip

Start small. A short test with a modest virtual-user count confirms everything is wired up correctly before you commit to a long, heavy run.

Note

Saved test users are a Vortex feature for authenticated scanning — Maelstrom load tests don’t use them. See authenticated scanning for that flow.

3. Launch and monitor

Launch the test. While it runs you’ll see live progress along with virtual-user metrics — the load building, response times, and errors updating in real time. You can follow a run to completion from this view.

Scheduling recurring tests

To run tests automatically on a cadence, use Maelstrom → Schedule and add entries to the schedule calendar. Scheduling is useful for catching performance regressions over time without launching each run by hand.

Note

Scheduling generally requires Growth or a higher tier, and very long or very large tests may also depend on your plan. Check the available options in the app.

Where to go next

• Reading a scaling report — interpret the results once your test finishes.