Skip to content

Latest commit

 

History

History
96 lines (70 loc) · 3.93 KB

README.md

File metadata and controls

96 lines (70 loc) · 3.93 KB
Raw

##Echo message performance test

In this performance test, a sample echo service with 2 operations were created.

  1. Accept a payload and respond the same payload back
  2. Accept a payload, write to a temp file, read that file and respond the same payload back Client was created with each subjected microservices framework. See echo-samples directory for the sample services that were created for each framework.

Prerequisite

  • apache2-utils - This performance tests are executed using ApacheBench. Therefore in order to run the tests, apache2-utils should be installed in the machine.

Throughput test

To measure the throughput, each of the above mentioned sample services were started and 1KB of payload was sent to each service repeatedly in varying concurrency levels using apache bench tool. After that the average throughput for each concurrency level is calculated and plotted for each framework.

EchoThroughput FileEchoThroughput

All services were run out of the box without any tuning separately on a 16 core 24GB server in JVM v1.8.0_51 with default configuration.

Performing the throughput test

Build the samples using the following command from perf-benchmark

./run.sh build

Run all tests using the following command from perf-benchmark

./run.sh

This script will perform the loads and provide you the average throughput, latency and all the percentiles for all the sample services.

You can customize the following parameters of the performance test by modifying the following values in excecute-tests.sh

  • concLevels - Space separated list of concurrency levels to test
  • perTestTime - Maximum time to spend on a single concurrency level
  • testLoops - Number of requests to perform for a sigle concurrency level
  • warmUpConc - Concurrency of the warm-up requests
  • warmUpLoop - Number of requests to send for warm-up

Memory Test

To measure the memory usage, above mentioned 1KB echo test was performed for each sample service. Then for each concurrency level the heap usage was measured and an average value for each concurrency level was calculated. These average heape usage values were plotted for each framework.

EchoMemory FileEchoMemory

Performing the memory test

For each service in echo-samples directory,

  • Build service
  • Start the service with GC logging enabled with time stamp (-Xloggc:gc-log-file.log -verbose:gc -XX:+PrintGCDateStamps)
  • Perform the test using the automated run.sh script as mentioned earlier
  • Get time range of each concurrency level from the output of the run-test.sh
  • Analyse the GC log for each concurrency level by matching the time range and calculate the average heap usage for each concurrency level

Latency Test

To measure the latency, above mentioned 1KB echo test was performed using same concurrency levels with 500000 requests per each concurrency level. Latency was measured using apache bench output. These values were plotted for each framework.

Note Due to higher latency values, some of the framework are been removed from the charts.

MeanLatency MedianLatency 90thPercentilLatency 95thPercentilLatency 99thPercentilLatency

Performing the Latency Test

Run the perf test samples one at a time and execute the run-latency.sh script.

./run-latency.sh   service-url

e.g.

./run-latency.sh http://localhost:8080/EchoService/echo

This will output the latency results to a latency-results.csv file. If you want to create seperate file you can pass the file suffix as 2nd parameter e.g.

./run-latency.sh http://localhost:8080/EchoService/echo msf4j

This will output the latency results to a latency-results-msf4j.csv