I Google’d the word “reliable” the other day. At the top of the results page was a definition from the Oxford Languages dictionary. I started thinking, what’s “reliable”? I glanced at my mobile phone. I felt it was pretty reliable. I can make and receive calls, I play games, battery life is pretty decent, photos are amazing… But it’s kind of new, so maybe that doesn’t count. It’s not really reliable, the jury’s still out.

This article shows some of the complexity that the k6 cloud backend handles when you run a k6 Cloud test.

Hi there, Here at k6, we’re constantly shipping new features to help our users get the most out of k6. In case you missed it, here’s a roundup of all the k6 and k6 Cloud news, updates, and improvements you should know about.

At a former employer, my Vice President of Engineering and Operations had a reputation for his language. He also had a reputation for his deep passion for things like site availability, incidents, downtime, and almost anything related to making sure the company's website was up and running, and especially that the end users were having a good experience using it.

I'm the technical writer at k6. If you're on this site, you probably know what k6 is. But, to reiterate the essentials: When I started five months ago, I knew I had some work to do because: Really, my "professional programming experience" culminated in some shell two-liners. Fortunately, the k6 team gave me a set of challenges to get up to speed. In this article, I go over the eight challenges the k6 team gave me and present the ways I solved them (I don't promise elegance).

For many companies, performance is the main reason to go with GraphQL. But is that a valid argument? Often developers compare GraphQL to REST APIs and see the N+1 requests (or over-fetching) as an important reason to go for GraphQL. Let's put that to the test and explore if GraphQL APIs actually can outperform existing REST APIs. For this, we'll take a GraphQL-ized REST API (from JSONPlaceholder) and test the performance of GraphQL and compare it to the REST approach.

As a software engineer here at Grafana Labs, I’ve learned there are two questions that commonly come up when someone begins setting up a new Loki installation: “How many logs can I ingest into my cluster?” followed by, “How fast can I query these logs?” There are two ways to find out the answers.

Rendezvous is a French word commonly used in the load testing word. It sounds so fancy! I believe Mercury first coined and implemented it (I may be wrong) in LoadRunner. NeoLoad has it with the same name, and JMeter calls it Synchronizing timer. But what is it really, and how may we use it? Rendezvous is a function that stops the virtual users when they reach that instruction in the script. The function makes them wait until more virtual users get to that step or a timer runs out.

In this tutorial, we'll show you how to store k6 logs in Loki for long-term storage and further analysis. We'll walk you through the steps to configure Loki in Grafana Cloud and enable k6 to send logs of your k6 tests to Loki.

Hello! Leandro here! Your k6 reporter. Today, we are reporting a story from the field. We just had a week of adventures and magical experiences at the 2022 StarEast event with real-life people for the first time in two years!