Skip to main content

Performance test your ASP.NET Core app using Bombardier

In the past I’ve always used Apache Bench, Fiddler or Visual Studio Load Testing to test the performance of my ASP.NET (Core) applications and API's. Recently I made the switch to Bombardier, a versatile HTTP benchmarking tool written in Go.

 If you have Go Go installed on your system, you can install Bombardier using the following command:

go get -u github.com/codesenberg/bombardier

But you can also download a binary compatible to your OS directly from the releases without the need to install Go.

I already started my ASP.NET Core application:

Running the tool is quite easy. Invoke the bombardier command with the target URL and some extra parameters:

bombardier -c 100 -n 1000 –l http://localhost:5042/WeatherForecast

This command will send 1000 requests with 100 concurrent connections to your application.

Bombardier will provide detailed statistics:

  • Reqs/sec: Requests per second.
  • Latency: Average response time.
  • Latency Distribution: Percentiles (50%, 75%, 90%, 95%, 99%) of response times.

You can customize Bombardier by adjusting parameters like concurrency, duration, and headers. Next step is to integrate Bombardier into our CI/CD pipeline or use it at scale with tools like Crank, but that is something I’ll leave for another post.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...