Execution

Using the Machmeter execute command to start executing a Performance POC template.

Table of contents

  1. Executing Performance Test
    1. Configuration File Definition
    2. Execution Command
  2. Cleanup
    1. Configuration File Definition
    2. Execution Command

Executing Performance Test

Executing perf test involves executing the execute command of machmeter with perf jmeter script as input. This script, when executed, will execute the input jmeter script.

This will execute the Performance test distributed across the GKE cluster created earlier.

For monitoring, server side performance can be seen in the spanner dashboard. For the client, the Grafana dashboard can be used. Please see below for details.

Configuration File Definition

Key name Description
namespace Name fo the test
jMeterTemplatePath Path to Perf Jmeter Script
jMeterParams.project Google Cloud Project Id
jMeterParams.instance Name of the instance to be created
jMeterParams.database Name of the database to be created
jMeterParams.connections Spanner Connection Counts

Please refer to the sample file for example values.

This is a sample file with the above defined configuration

Execution Command

Ensure you have the GKE credentials configured via: gcloud container clusters get-credentials CLUSTER_NAME --region=COMPUTE_REGION

java -jar target/machmeter/machmeter.jar execute path-to-config-file.json

Cleanup

Cleanup involves executing the cleanup command of machmeter with spanner instances config, GKE cluster config and path to the data load SQL script created in the earlier steps. Here, the config file remains the same as in Setup. This step deletes the instances and clusters created.

Configuration File Definition

This is a sample file with the above defined configuration.

Refer to the Setup section for details on the config file.

Execution Command

java -jar target/machmeter/machmeter.jar cleanup path-to-config-file.json