Visualize Web Framework Benchmark Result

Recently, I found the latency result in Web Frameworks Benchmark is weird.

It turns out that the data table shows the wrong unit. It display us as ms. So I submit a PR to fix it.

After the fix, the data looks good, but the table is still hard to read, especially when you want to compare multiple frameworks and languages.

So I did draw some graphs to visualize the result.

QPS

Here is the QPS of each framework with 64, 256 and 512 concurrent clients.

From the right parts of it, you can see that some framework's QPS increase as clients count increase.

It means that, these fast frameworks are still not reaching their limits, and we need to generate more load.

Latency

Nowadays, we also care about user experience, and latency is a common metric for it.

As load increases, latency will increase.

The Nickel framework is pretty amzing, it provides really low and consistent latency.

Latency and QPS

Now we have latency and QPS data, we can combine them in the same graph.

For average latency and QPS, it's almost a straight light.

For P99 latency and QPS, it becomes much messy, but you still can see the trend.

Kauruus
CC BY-SA 4.0
Website built with Franklin.jl and the Julia programming language.