Latest Posts

k6

k6 in ThoughtWorks Technology Radar

ThoughtWorks is a global software consulting company that releases an insightful Technology Radar twice a year as a round-up of the current state of technological techniques, platforms, tools, and languages or frameworks. We were pleasantly surprised to see k6 featured in the Tools section of Volume 23, the latest volume of the Technology Radar.

k6

Comparing k6 and JMeter for load testing

When I joined the k6 team in late November, the foremost question on my mind was "How does this compare to JMeter?" You see, I come from a performance testing consulting background, and in the last few years, JMeter has been far and away my tool of choice. So what am I doing on the k6 site, talking about how much I love JMeter? Well, firstly, it turns out that the k6 team is pretty open and transparent, especially about potential improvements in k6.

k6

Testing without limits: xk6 and k6 extensions

k6 v0.29.0 introduced xk6 and k6 extensions to the k6 community. 🎁🎉💪 You can now extend the functionality of k6 using Go-based k6 extensions and import them as JS modules in your k6 script. This feature opens the gates for anyone to use existing k6 extensions and write custom Go extensions for special requirements. Before this release, importing JavaScript libraries was the only possibility to extend k6.

k6

Performance testing gRPC services

v0.29.0 contained a lot of interesting features. Have a look at the release notes for details! gRPC is a light-weight open-source RPC framework. It was originally developed by Google, with 1.0 being released in August 2016. Since then, it's gained a lot of attention as well as a wide adoption. In comparison to JSON, which is transmitted as human-readable text, gRPC is binary, making it both faster to transmit and more compact.

k6

Load Testing a Caddy Web Server on a GCP F1-Micro instance Using K6

I used the K6 load testing framework to benchmark the Compute Engine f1-micro and Caddy web server hosting this site. With CloudFlare caching turned off, the server was able to serve an onslaught 800 virtual users continuously reloading the page (while maintaining a median request duration of <400ms), but started dropping requests when increasing the load further. This is fine.