Skip to content

Tutorials

Install OctoPerf on Kubernetes With Our Helm Charts

Most of our self-hosted customers run OctoPerf Enterprise Edition with Docker Compose. But more and more of them run everything else on Kubernetes, and they ask how to install OctoPerf there too. We actually maintain two Helm charts for that: one for the OctoPerf server, and one for an agent that runs the load generators as pods of the cluster.

In this blog post I install OctoPerf 18 on a local minikube cluster with these charts, register a Kubernetes agent and run a small load test against our demo shop. Everything runs on a single Linux laptop, and the same charts work on a real cluster with a few more settings.

Migrating Gatling Simulations to OctoPerf With an AI Agent

Migrating a load testing project is rarely difficult, but it takes time and it's easy to give up halfway. That's why OctoPerf 18 comes with a Gatling migration playbook for AI agents.

In our NeoLoad and LoadRunner walkthroughs, the projects were converted into JMeter Virtual Users. A Gatling simulation is code, so here it stays code: the agent rewrites it as a K6 script, and its injection profile becomes an OctoPerf scenario. In this blog post I show the actual prompts and what the agent answered, and both projects can be downloaded.

Running K6 Scripts on OctoPerf

We just released OctoPerf 18 and its main addition is a new load testing engine: K6. You can now import your K6 scripts and run them without changing a single line, next to JMeter and Playwright Virtual Users, in the same scenarios and the same reports.

In this blog post I import a K6 script that browses our public demo shop, validate it, run it and go through the results. The scripts can be downloaded if you want to follow along. I will finish with the things that work differently than with JMeter.