The package (performance-ballerina-distribution-${version}.tar.gz) built by the distribution maven module is the package required for Ballerina performance tests from this repository.
3 ballerina files are present with the package that will be used for testing
helloworld.bal
passthrough.bal
transformation.bal
The (performance-common-distribution-${version}.tar.gz) package is also required for performance tests.
The scripts in this repository depend on the scripts in "performance-common" repository.
This package must be extracted in user home directory of the JMeter node and the Ballerina node used for the performance tests.
In addition, please make sure to extract the "performance-common" package to all nodes and install Java, JMeter, and SAR to all nodes by using scripts provided.
See following sections for more details.
The "ballerina-scripts" directory has the scripts related to Ballerina and the configurations. These scripts must be run in Ballerina node.
Following sections have more details about each script.
The setup.sh script is the only script you need to run to set up and configure Ballerina. A ballerina distribution
should be copied to the home directory og the Ballerina node. This script will extract the distribution and copy the
bal files that will be used to do the performance tests. The name of the ballerina distribution should be given as a
parameter
How to run:
./setup.sh ballerina-runtime-0.970.0
This script starts the given Ballerina service with the given Java heap size and given flags
How to run:
./ballerina-start.sh 1G helloworld.bal -e b7a.http.tracelog.console=true
Inside "jmeter-scripts", directory there are two scripts to run the performance tests and create a summary CSV from the JMeter results.
The run-performance-test.sh script runs the performance tests for different test scenarios. This script must be used
in the JMeter node
This script is using ssh config to connect with other nodes from JMeter client and get server metrics and log files.
Therefore, it is important use a configuration as follows in ~/.ssh/config
Host ballerina
HostName x.x.x.1
User ubuntu
IdentityFile ~/keys/ballerina.pem
There are multiple parameters inside the script and the values should be changed as required.
| Parameter | Description |
|---|---|
| message_size | The different number of message sizes (payloads) in Bytes. This is an array. |
| concurrent_users | The different number of concurrent users. This an array and the brackets are important. |
| ballerina_files | The different ballerina files to be run. This is an array. |
| ballerina_flags | The different environment parameters to configure the ballerina service. |
| ballerina_flags_name | The symbolic name given to each ballerina_flag. The array size must be same as the ballerina_flags array. |
| ballerina_heap_size | The heap size to be used to run the ballerina service. |
| ballerina_host | The hostname or IP of the Ballerina node. |
| api_path | The api path of the ballerina service to which requests should be sent. |
| ballerina_ssh_host | The ssh host for the Ballerina node. |
| test_duration | Duration of the test in seconds. |
| warmup_time | The warmup time in minutes. This is used for JTL Splitter, which is from performance-common |
After changing parameters, the performance tests can be started from the script in the JMeter node.
It's recommended to run the tests in nohup mode.
For example:
nohup ./run-performance-test.sh > test.out 2>&1 &
The results of performance tests will be saved in results directory.
After the performance tests are completed, a summary CSV for all results can be created using this script file.
The script expects the GCViewer jar file to analyze GC logs. The latest GCViewer JAR file can be downloaded from Maven
Copy the script inside the results directory before running.
How to run:
./create-summary-csv.sh /path/to/gcviewer*.jar