Configuring Mixed Concurrency for Different Interfaces Using RunnerGo in Performance Testing

Hello everyone, today we will show you how to use RunnerGo to configure different concurrency numbers for different interfaces (mixed concurrency) in performance testing.

We take a simple news app scenario as an example, which includes the following interfaces: login, home, detail, collect news, news list, and add news.

The interface relationship is as follows: the user goes from the login or home interface to the detail interface, and from the detail interface to the collect news, news list, and add news interfaces.

Configuration steps:

Step 1: In the performance test plan management, create a new plan for the news app.

Step 2: Click "Import Scenario" and import the interfaces related to the news app scenario described above.

Step 3: After the import, each interface module can set an interface weight, which represents the percentage of the total concurrency allocated to that interface; the default weight is 100.

We illustrate mixed concurrency with a total concurrency of 100. Set the detail interface weight to 80, the collect‑news interface weight to 80, and the add‑news interface weight to 50.

During the actual test, the collect‑news concurrency is 64, calculated as 100 × 80% × 80% = 64, and the add‑news concurrency is 40, calculated as 100 × 80% × 50% = 40.

This completes the operation steps for using RunnerGo to configure mixed concurrency. A video tutorial is also provided for those who need visual guidance.

If you encounter any other issues while using the product, feel free to leave a comment or private message under the official account; we will be happy to assist you.

Official website: https://www.runnergo.com

GitHub: https://github.com/Runner-Go-Team

Gitee: https://gitee.com/Runner-Go-Team