Skip to content

Conversation

@akselkvitberg
Copy link
Member

Adopt K6 as the primary load testing tool after evaluating alternatives. Documented the decision-making process, including context, background, and risk/benefit analysis.

Adopt K6 as the primary load testing tool after evaluating alternatives. Documented the decision-making process, including context, background, and risk/benefit analysis.
Added note about BCC Fellestjenester's non-profit account on Grafana Cloud for cost-effective cloud execution options.
Copy link
Member

@KillerX KillerX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At BCCM we are using k6, for pretty much the same reasons described here. It's also easy to prepare and test the test locally.

Our applications require robust load testing to ensure performance and reliability under high user demand. The team needs a tool that supports complex workflows, is easy to use, and integrates well with our existing technology stack.

### Background
During development of the Privacy and consents web app, load testing was being done using a custom tool. This proved to be too time consuming, due to complex behaviour depending on which load profile was being used. Therefore, we decided to evaluate existing load testing tools that could better meet our needs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also note that previous experience with loader.io only seemed to work for very simple use cases.
Several other tools investigated previously seemed overly complex to work with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants