artillery VS Bulma

Usually, I would let organic users be my load test. However, I am working on a project that has an anticipated load on a new-to-my-team stack, so I'm looking into ways to load test.

I've seen tools like k6 (https://k6.io/), Artillery (https://www.artillery.io), and JMeter (https://jmeter.apache.org/).

I've been using Artillery, but it's hard to visualize the results.

What do you use?

This week was Tracetest’s first-ever Launch Week. We’ve been working on a major integration with Artillery for the last month and our team is beyond excited to share it with you all!

I found a tool for load testing called Artillery. Following this guide I installed Artillery and began research for the test configuration.

This is a great blog post! just taking the opportunity here to comment on this:

> Finally for full scale high fidelity load tests there are relatively few tools out there for browser based load testing.

It exists as of a few months ago and it's fully open source: https://github.com/artilleryio/artillery (I'm the lead dev). You write a Playwright script, then run it in your own AWS account on serverless Fargate and scale it out horizontally as you see fit. Artillery takes care of spinning up and down all of the infra. It will also automatically grab and report Core Web Vitals for you from all those browser sessions, and we just released support for tracing so you can dig into the details of each session if you want to (OpenTelemetry based so works with most vendors- Datadago APM, New Relic etc)

So not to stress test Momento or AWS' Lambda, I wanted to build a small but stable 10-minute workload that hits the Momento Topic API and then let Momento trigger the FunctionURL to run the Lambda code. I wrote a small Artillery config file that ramps up to 20 users and then sustains that for the duration. Again, the script is simple to trigger the work.

Tool Spotlight: Featuring insights on how Artillery and Gitpod can enhance and streamline the benchmarking process.

curl is fantastic. There's also HTTPStat which provides a waterfall visualization on top of curl timings: https://github.com/reorx/httpstat

There's also Skytrace (made by yours truly), which provides timing info as a waterfall visualization inspired by HTTPStat + lots more (syntax highlighting for responses, built-in JMESPath support, command-line assertions and checks etc) - https://github.com/artilleryio/artillery/tree/main/packages/...

https://www.artillery.io/

I know it's an annoying answer, but it depends on your application. The only true way to know is to test it using a load tester like artillery. Measuring performance is a fundamental part of any optimisation (otherwise how do you know?), so it's a great idea to be using tools like this anyway.

For this test I have used artillery.io with the following configuration:

Tailwind is great, but creating everything from scratch is annoying. A nice base of components which can be extended with tailwind would be great. There are a few tailwind frameworks like Flowbite, Daisy Ui, but I like Bulma, PicoCSS and Bootstrap.

I would talk about building the frontend, but it is just a single page React app I built quickly. It does use a CSS library called Bulma, which is similar to tailwind and worth checking out. I did spend a day implementing a login/signup page, but this was just for the learning experience, and not what I wanted in the final product.

After finding a few spare hours I decided to address the alerts and update some my dependencies. I spent several hours debugging my Gatsby site after doing some recommended npm package updates. My UI class library Bulma was not being loaded by my sass-loader module. (I later learned that they migrated to dart-sass so I guess the fix should have been a pretty easy). Nonetheless, this prompted me to rethink my entire static site generator stack and got me curious about some other options. Why have these unnecessarily complex dependency chains? At that point I was almost too hesitant to even touch my package.json file. That's just silly.

Oh wow, quite happy about this, for a while it seemed the project was abandoned, really glad Jeremy keeps working on this :) The new website (https://bulma.io/) also looks very slick. I could totally see that he'd be able to monetize this like Tailwind, it's a really well thought-out framework with a good compromise between responsiveness, utility classes and components.

So, our post.component.html component is the generic page where all posts will have their content loaded. Here, the classes are from the Bulma CSS framework, and the template looks like this:

This is a pretty basic HTML that contains a form with a couple of form fields and a submit button. To make styling a little easier, I opted to use Bulma. But that’s entirely optional, and does nothing to impact our app.

Since v1.9.0 release, the Gowebly CLI includes support for Bootstrap and Bulma CSS frameworks.

Bulma is a lightweight and modern CSS framework that simplifies the styling of your web projects. It offers a clean and intuitive set of classes to structure and design your HTML elements, providing a quick and easy way to create visually appealing layouts. Bulma is responsive and mobile-friendly, making it an excellent choice for developers who want a straightforward and flexible solution for their projects. Whether you're a beginner or an experienced coder, Bulma's simplicity and versatility make it a popular option for building stylish and responsive web interfaces without the need for extensive customization.