Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2021, 15 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Sponsored Session: HAProxy Technologies - Benchmarking 5 Popular Ingress Controllers

Description

Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Sponsored Session: HAProxy Technologies - Benchmarking 5 Popular Ingress Controllers

Speakers: Daniel Corbett

Performance has never been more important than in a cloud-native world. Cloud-hosted resources cost money and a slow-loading application can cause a suboptimal ROI. Have you taken the time to tune your Kubernetes ingress controller and proxy? Many organizations don't until it's absolutely necessary, and most users will typically run a default, out-of-the-box configuration.

In this demo, we benchmark five popular ingress controllers and put them head-to-head against each other with their default configurations:

• Envoy
• HAProxy
• NGINX
• NGINX Inc.
• Traefik

We measure their average requests per second, latency percentiles, and user-level CPU usage; We monitor for any errors that are produced in order to go beyond performance and test reliability. You can verify the results yourself by downloading the GitHub repository and reproducing our tests. Who will come out on top? Watch the demo to find out!

In this demo, we benchmark five popular ingress controllers and put them head-to-head against each other with their default configurations: Envoy, HAProxy, NGINX, NGINX Inc., and Traefik.

A

Hello thanks for taking the time to watch the demo in the following: I'm going to run some out of the box benchmarks against several ingress controllers. First, a little about me. My name is daniel corbett and I am the director of product at ha proxy technologies.

A

Benchmarking is a science in and of itself, but many users do not have the time required to perform head-to-head tests against the wide range of ingress controllers that are available.

A

Understanding how your ingress, controller and proxy performs is important, as poor performance can cause you to use excessive resources which ultimately translates to lost money, especially in a cloud native world, can also lead to a sub-optimal user experience. For your end clients.

A

However, when it comes to tuning various pieces of the infrastructure, many users get lost in the abyss of information online or just do not even think it's something they need to do. This means that many users end up running out of the box configurations.

A

This demo is going to focus explicitly on those out of the box configurations to find out which ingress controller performs the best in a new setup.

A

I've included a link to the full architecture, setup guide and code, to reproduce these benchmarks on the aha proxy technologies github located on the url at the top of this slide.

A

For this demo, I've configured a six node kubernetes cluster running on c5 extra large instances.

A

One of the nodes has been dedicated specifically to the ingress controllers. The other five are where we will run our traffic injectors.

A

I have five pods running a standard, echo application in which the ingress controllers will be monitoring for changes and routing traffic to in these tests. I'm testing with envoy with the contour as the ingress controller, the aha proxy ingress controller, two different nginx singers controllers and traffic.

A

For each of these, I will be running the latest versions. At the time of this benchmark, which are shown in the table, you may be wondering why I have two different nginx ingress controllers listed. This is because there are two completely different open source projects.

A

One is a kubernetes community driven project and the other is directly from nginx inc. The biggest difference is the kubernetes community. Driven one has a very complex configuration and harnesses lua for many of the dynamic capabilities, while the nginx inc one is a bit more slimmed down and does not use lua from here on out I'll refer to the kubernetes community driven project as nginx and the other as nginx inc for the actual tests. I will use the tool hey during the test. I will maintain 50 concurrent workers from 5 traffic, injecting pods.

A

Each ingress controller will be benchmarked for a total of 6 minutes. Don't worry I'll. Do some post-processing magic to skip through the boring parts.

A

During this time I will also scale the pods up to 7 and back down to 5 with 30 second intervals in between scale outs.

A

This will happen approximately three times and then I will make several changes to the ingress controllers themselves, such as adding and removing course headers and adding and removing path rewrite rules. I will also issue a sleep in between each change for 30 seconds.

A

At the end of the benchmarking, we will graph the average request per second, the 75th 95th and 99th latency, percentiles and user level. Cpu usage we'll also graph the number of http error codes that we receive.

A

Let's get the benchmark started.

A

I'll be running a shell script that will handle running the benchmark as well as collecting and graphing the data. Let's go ahead and start the benchmark.

A

A

The test is completed: let's examine the graph data.

A

If we look at the first chart, we're able to see that h, a proxy came on top averaging, approximately requests 46.000 second with envoy in second place at around eighteen thousand. We can see that traffic came in last at around twelve thousand requests per second.

A

If we look at the latency percentiles, we can see that h.a proxy had the lowest 75th 95th and 99th percentiles. In fact, its 99th percentile is half of envoys who came in that. Second traffic and nginx inc were neck and neck for a close third, and we can see that nginx came in last with a massive spike for the 99th percentile metrics.

A

Looking over at user space, cpu usage, we're able to see that h, a proxy and nginx inc were neck and neck in cpu usage with 48 percent and 46 cp usage respectively.

A

Both envoy and traffic came in around the mid 70 range.

A

Now, let's look at how many http errors were produced by each proxy.

A

It appears that neither ha proxy nor nginx inc produced any http errors, but traffic produced a little over 800 502 errors, nginx produced 50 502s and eight 504s and envoy produced 21 503 errors.

A

That concludes our demo. Aj proxy has a reputation for being the world's fastest and most widely used software load balancer in the world. For a reason, give it a try today and you'll be certain that it's out of the box configuration will supercharge your kubernetes.

A

Environment you.