Producing Load on Event Streams with Workload Application

IBM Event Streams provides a high-throughput producer application you can use as a workload generator to test message loads and help validate the performance capabilities of your cluster.

You can use one of the predefined load sizes, or you can specify your own settings to test throughput.

Introduction

In this lab we will install the sample application and test running some load.

At the end of this lab your should be able to install and configure the sample application and run load tests.

Log on to the master node as shown previously.
Go to Event Streams UI as shown previously.
Go to Toolbox.
Click on View in GitHub on the Workload Generator Application.
When you arrive at the github repo, scroll down to the README.md file section and click the hyperlink under Getting Started.
Go to Releases.
Download the sample application (es-producer.jar) under Latest release.

If you get a warning about the download harming your computer, click Keep.
Open a command window.
Move the downloaded file to your home directory..
```
mv ~/Downloads/es-producer.jar ~/
```
Enter the following command to create the config file for the application:
```
java -jar es-producer.jar -g
```
The config file has been created (producer.config).
Open this file in a text editor with the following commannd:
```
gedit producer.config
```
You will be prompted for student’s password. Enter Passw0rd!.
We now need to edit this file to add the following information:
- bootstrap.servers
- ssl.truststore.location
- sasl.jacl.config.
To get the required information we need to go back to the Topics view. We will use the eslab topic that was created previously.
In the Topics view, click on the eslab topic to open it.
Click on the Connection to this topic tab.
Click on the Copy broker URL box to get the URL. (save this somewhere to be added to the config file later).
Scroll down a little until you see the Certificates section.
We are using a java application so click on the Download Java truststore.
Copy this file to your home directory for later use.
Under API key, enter a name for your application - es-producer. Click Produce only.
The topic is filled in for you. Click Generate API key.
As you can see, the API key is generated. You should copy the API key and save it where you saved the bootstrap server value or download the key as a file (es-api-key.json). Copy this file to your home directory.
Close the Topic connection pane by clicking the X.
We now need to go back to the text editor and update the configuration file with the correct information.
Enter the connection URL that you saved previously as the bootstrap.servers parameter
Enter the full path (including filename) of the keystore file you downloaded previously (note that in this example this file has been moved to the home directory).
Open the downloaded es-api-key.json file and copy the apikey.
Enter the API Key as the password parameter (do not change the username as this is already set to the required value of “token”).
Save the file.
Go back to terminal window.

You create a load on your IBM Event Streams Kafka cluster by running the es-producer.jar command. You can specify the load size based on the provided predefined values, or you can provide specific values for throughput and total messages to determine a custom load.

To use a predefined load size from the producer application, you use the es-producer.jar with the -s option:

java -jar target/es-producer.jar -t <topic-name> -s <small/medium/large>

We will start with a small load:

Enter command:

java -jar es-producer.jar -t eslab -s small

After listing the parameters that will be used you will see the messages being sent (this should be fairly quick so if you are not seeing this, check for errors either on the screen or in the producer.log file).
The run will finish with a message that indicates the number of messages sent and the overall performance.
We can go back to the Event Streams UI and have a look at the Monitor for our test.
Click on the Monitor tab.
We can see the incoming messages from our “small” test.
There is not really very much interesting going on here (more about Monitoring will be contained in another lab). However, lets run a large load and we will be able to watch the monitor moving as the messages are loaded.
Go back to the terminal window and rerun the load test but this time send a large sized load.
```
java -jar es-producer.jar -t eslab -s large
```
This is going to take considerably longer than before so go back to the Events Streams UI.
You will see that the volume of data is increasing.
Click on the past 15 minutes label for a more detailed view.
We can see both the small load run from earlier and now the large load run in progress.

If you have time you may wish to experiment with options other than the defaults. The details of all of the available parameters can be found at:

Parameters for Workload App

If you still have your Consumer app running, you may also wish to start consuming the messages and have a look at the Monitor.

Congratulations

You have successfully created a workload generator application and ran some loads through Event Streams. You are now ready to create an Event Streams connector to MQ.

Continue to Lab 6 - Kafka Source Connector for MQ

IBM Event Streams Toolbox - IBM Cloud Private

Producing Load on Event Streams with Workload Application

Introduction

Congratulations