Testing on Solo

Using Network Load Generator with Solo

Mon, 01 Jan 0001 00:00:00 +0000

Using Network Load Generator with Solo

The Network Load Generator (NLG) is a benchmarking tool that stress tests Hiero networks by generating configurable transaction loads. Use it to validate the performance and stability of your Solo network before deploying to production or running integration tests.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you have a running Solo network and are familiar with the basic Solo workflow.

Step 1: Start a Load Test

Use the rapid-fire load start command to install the NLG Helm chart and begin a load test against your deployment.

Community Contributions

Mon, 01 Jan 0001 00:00:00 +0000

How to Contribute to Solo

This document describes how to set up a local development environment and contribute to the Solo project.

Prerequisites

Node.js (use the version specified in the repository, if applicable)
npm
Docker or Podman
Kubernetes (local cluster such as kind, k3d, or equivalent)
task (Taskfile runner)
Git
K9s (optional)

Initial setup

Clone the repository:

git clone https://github.com/hiero-ledger/solo.git
cd solo

Install dependencies:

Solo CI Workflow

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This guide walks you through integrating Solo into a GitHub Actions CI pipeline - covering runner requirements, tool installation, and automated network deployment. Each step installs dependencies directly in the workflow, since CI runners are fresh environments with no pre-installed tools.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you are familiar with the basic Solo workflow and the solo one-shot single deploy command.

This guide assumes you are integrating Solo into a GitHub Actions workflow where each runner is a fresh environment. The steps below install all required tools directly inside the workflow rather than relying on pre-installed dependencies.