Welcome to OctoPerf's blog, where we embark on a journey through the dynamic landscape of load testing, a crucial aspect of ensuring your applications thrive in the face of user demands.
Whether you're a seasoned performance engineer or just diving into the world of load testing, our blog is your go-to resource for insights, best practices, and cutting-edge tools.
JMeter Load-testing
Load-testing using the n°1 open-source solution: Apache JMeter™.
Real-Browser Load-testing
Load-testing using real-browser solutions like Playwright and Selenimum Web-Driver.
Load-testing Methodology
Load-testing methodology and tools comparison.
OctoPerf's releases
Stay tuned on the JMeter™ Performance Center latest releases: OctoPerf!
Whether you're a developer aiming to optimize your code, a QA engineer ensuring application resilience, or a business owner safeguarding user satisfaction, load testing is your ally. Join us on this expedition into the heart of performance excellence.
Are you ready to transform your understanding of load testing? Let the journey begin!
OctoPerf 18.0.0 is out! In version 17 we separated the injection engine from JMeter, and this release is where it starts to pay off: K6 is now available as a load engine next to JMeter and Playwright. Playwright Virtual Users also measure the Core Web Vitals of every page they open.
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 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.
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.
Our BlazeMeter to OctoPerf Maven plugin is archived. What replaces it is not another tool to install: OctoPerf 17 ships a BlazeMeter migration playbook for AI agents.
Real prompts, real output, run against a real BlazeMeter account.