Skip to content
This repository has been archived by the owner on Jul 7, 2023. It is now read-only.

Latest commit

 

History

History
52 lines (35 loc) · 2.99 KB

README.md

File metadata and controls

52 lines (35 loc) · 2.99 KB
Raw

xk6-temporal

k6 extension for testing/benchmarking Temporal.

Note: This project is still a spike. The API may change at anytime as we learn from experience.

We recommend that you use this k6 extension alongside our benchmark workers which provide some pre-written workflow and activity workers that you can make use of for benchmarking. You can of course bring your own workflow and activity workers if you want to benchmark a closer simulation of your specific workload.

Our benchmark workers are available at: https://github.com/temporalio/benchmark-workers

Usage

This extension is available compiled into k6 as docker image for use in Docker or Kubernetes setups.

You can pull the latest image from: ghcr.io/temporalio/xk6-temporal:main.

In future we will provide releases with appropriate image tags to make benchmarks more easily repeatable.

Before you run a benchmark make sure your workers are deployed and scaled as required. If you would like to use our pre-written benchmark workers rather than your own you can find details of how to do that on the (benchmark-workers site)[https://github.com/temporalio/benchmark-workers].

To run one of our example benchmark scripts against Temporal in a Kubernetes cluster you can use:

kubectl run k6-benchmark -ti \
    --image ghcr.io/temporalio/xk6-temporal:main \
    --image-pull-policy Always \
    --restart Never \
    --env TEMPORAL_GRPC_ENDPOINT=temporal-frontend.temporal:7233 \
    --
    k6 run ./examples/start-complete.js

You will see the benchmark progress and the final statistics on screen.

Metrics

Currently the Temporal Client that the extension creates have their metrics wired into the k6 system. This has the benefit of being visible inside the k6 infrastructure for use in k6 checks and thresholds. The downside is that these metrics cannot be scraped into Prometheus to appear in the same way that SDK metrics normally would if exported from an application. This is because k6 adds a prefix to metrics and also handles histograms differently by pre-processing them into p95 and so on, as opposed to Temporal SDK's standard behaviour of sending them on to Prometheus as it's native histogram type. We are interested in feedback for what we might improve here.

Having said all that, if you do have Prometheus setup we recommend that you send the k6 metrics to your Prometheus instance to more easily tie k6 results to changes in Temporal metrics. To do this you can configure k6 to push metrics to Prometheus by running a benchmark like so:

kubectl run k6-benchmark -ti \
    --image ghcr.io/temporalio/xk6-temporal:main \
    --image-pull-policy Always \
    --restart Never \
    --env TEMPORAL_GRPC_ENDPOINT=temporal-frontend.temporal:7233 \
    --env K6_PROMETHEUS_REMOTE_URL=http://temporal-prometheus.temporal:9090/api/v1/write \
    --
    k6 run -o output-prometheus-remote ./examples/start-complete.js

Note: Your prometheus instance will need to have remote write enabled for the metrics to be receieved, this is often not enabled by default.