Getting started with Maxoperf

Maxoperf turns ad hoc performance scripts into repeatable tests that your team can review, with shared results. This guide takes you from a new account to a finished run in a few minutes.

Authorize before you test

Only test systems you are explicitly authorized to load. Maxoperf records the target URL and the source locations of the test.

Create and run your first load test.

Before you start

You need:

• An account on Maxoperf and an invitation to a workspace, or your own new workspace.
• A target URL or test script you are allowed to load.

Run the path end to end

1. Sign in to the console and pick the workspace and project you want the test to live in. If you do not have a workspace yet, create one. Most teams start with one per organization. See Accounts, workspaces, and projects.

2. Create your first test. From the project page, click New test. Give it a clear name and a short description so teammates know what it covers.

   

   The New test form. Fill in the name and description, then move down to the scenario, load, and location sections.

3. Choose a small load profile. For a first run, keep the virtual-user count and duration small. You want to prove the scenario works. Finding the breaking point comes later.

4. Pick locations. Use a managed cloud location for public targets, or a private location for internal systems. See Managed and private load locations.

5. Start the run. Maxoperf provisions runners and starts generating load. Watch latency, throughput, and errors arrive on the live results page.

6. Read the result. When the run finishes, open the run detail page to inspect latency percentiles, error breakdowns, and runner health. Add tags or notes so you can compare the next run with it. See Read run results and logs.

   

   After the run finishes, the Run detail Overview tab shows status, latency, throughput, and virtual users.

What to do next

When your first run is green, decide which test workflow your team wants:

• One-off tests before each release: start from the same test and re-run it.
• Scheduled regression tests: see Schedule recurring tests.
• Automated tests from CI: see Run tests from CI.

Where to go next

• Run your first test: a longer walk-through with file uploads.
• Upload test files: bring existing Taurus, JMeter, or k6 assets.
• Read run results and logs: what to look at when a run finishes.