loadster

Scale Your Load Testing Efforts with Loadtester.

Loadtester is a powerful tool that helps you simulate millions of concurrent users by distributing load tests across multiple computers.

Docs | Demo | Help And Support

Install - ref

npm

npm install loadster -g && loadster

Note: In case of permission issue try it with sudo.

Script for linux and macOs versions

curl -sL https://raw.githubusercontent.com/cirnum/loadtester/main/installer/bash/install-loadtester.sh | sudo bash && loadster

binary

https://docs.perfcheck.com/installation#install-with-shell-script

Run as a worker

loadster --WORKER=true --MASTER_IP="MASTER_NODE_IP_OR_DNS"

You have the convenience of directly incorporating a worker node into the master web UI and synchronizing from there, eliminating the need for the MASTER_IP argument.

--HOST_URL= (useful when your application is running within a Docker container or if you need to assign a specific DNS for the master) Optional.

Steps: Server > Add New Server > Sync With Master ( In Web ui )

How to Use

Scale Your Load Testing Efforts with Loadtester.

Loadtester is a powerful tool that helps you simulate millions of concurrent users by distributing load tests across multiple computers.

Steps:

• Install Loadtester on your local machine or server.
• Use the intuitive graphical interface to design your load test scenario.
• Configure test settings such as the number of virtual users, test duration, and test environment.
• Distribute the load test across multiple machines or servers using the Loadtester controller.
• Monitor test results in real time using built-in reporting and analysis tools.
• Analyze test results to identify performance bottlenecks and optimize your system for maximum scalability.

Try Loadtester today and discover how it can help you improve the performance and scalability of your application or website.

Create server

Note - because of resource limit (CPU, bandwidth) you can configure

as many servers as you can run the test script across all the servers at the same time.

Possible ENV to pass while running the Binary

Env Name	Default	Description
WORKER	false	User can run loadtester as a worker or as a Master node
MASTER_IP	empty	If the user runs the node as a Worker then the worker node can accept the MASTER_IP env which is the actual master ip
HOST_URL	empty (Auto Detect)	If the application is running inside a Docker container or if the Master Node has a particular DNS address, this information will be transmitted to the child node for synchronization and future updates.

Download binary - ref

1. `Darwin amd64` - For Mac user
2. `Darwin arm64` - For Mac users (new Mac)
3. `Linux amd64` - Linux arch `amd64` users (64-bit system)
4. `Linux arm64` - Linux arch `arm` users (32-bit system)
5. `windows amd64` - Windows Users

Creating the first request

• Click on Request tab on header

• Fill out the form

• Url - stress testing target Url

• Client - Total client wants to initiate - use 100 to 1000 (depends on your cores and cpu)

• Time - Till the time you want to run these requests

• Select Method Get Post whatever your stress url serve

AWS integration (Required Env)

Env Name
AWS_ACCESS_KEY
AWS_SECRET_KEY
AWS_REGION

Request Page

Request Stats - You can check request stats here

AWS section - Create multiple nodes for distributed testing

Check, enable, and disable the connected nodes from the server section