The method and process of JuAPI Gateway performance Test

This article mainly introduces "JuAPI gateway performance test method process". In daily operation, I believe many people have doubts about JuAPI gateway performance test method process. Xiaobian consulted various materials and sorted out simple and easy operation methods. I hope to help you answer the doubts of "JuAPI gateway performance test method process"! Next, please follow the small series to learn together!

API gateways planned for testing include:

hyperapiKonggokuAPISIX

The test is just the simplest request forwarding scenario, visiting a static page on nginx upstream of the gateway, all gateways configured for apikey authentication and enabling their respective RateLimit plugins.

Let's cut the crap and get to the results:

See Benchmark section of project documentation for specific configuration and running test commands of each gateway in the test.

Baseline

First of all, we used ab to test the performance of nginx returning a static page as a test benchmark. Under 100 concurrent 500,000 requests, the CPU of Nginx server is above 90%, and the number obtained is QPS: 38756.59.

hyperapi

Hyperapi is the name given to the JuAPI gateway on github and is an open-source API gateway developed based on the rust language, the tokio asynchronous framework and the hyper library.

In this test, the gateway service was started by a handwritten static configuration file. In the test run of 200 concurrent 500,000 requests, the CPU utilization rate of the hyperapi process was close to 100%, the CPU utilization rate of the backend nginx process was about 20%, and the final QPS was 10164. There were no request errors and 99% request delays.