I use Caddy in our company.
On our CentOS VMware machines, we use brew to install it brew install caddy. Could also just install it via go get but I decided against it (upgrading caddy looked cumbersome back at that time).
Here is a super simple benchmark we did:
brew install nginx caddyindex.html with a link to existing index.css & existing index.js file and a non-existing bla.css entry in the meta tag10000 / 10000 100.00 %
Summary:
Total: 16.3046 secs.
Slowest: 1.2671 secs.
Fastest: 0.0040 secs.
Average: 0.1616 secs.
Requests/sec: 613.3227
Status code distribution:
[200] 10000 responses
Response time histogram:
0.004 [1] |
0.130 [4517] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
0.257 [4230] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
0.383 [847] |∎∎∎∎∎∎∎
0.509 [280] |∎∎
0.636 [73] |
0.762 [28] |
0.888 [12] |
1.015 [7] |
1.141 [2] |
1.267 [3] |
Latency distribution:
10% in 0.0650 secs.
25% in 0.1080 secs.
50% in 0.1360 secs.
75% in 0.1890 secs.
90% in 0.2780 secs.
95% in 0.3560 secs.
99% in 0.5261 secs.
10000 / 10000 100.00 %
Summary:
Total: 2.8187 secs.
Slowest: 0.1650 secs.
Fastest: 0.0040 secs.
Average: 0.0280 secs.
Requests/sec: 3547.7120
Status code distribution:
[200] 10000 responses
Response time histogram:
0.004 [1] |
0.020 [5195] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
0.036 [3158] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
0.052 [841] |∎∎∎∎∎∎
0.068 [153] |∎
0.084 [140] |∎
0.101 [62] |
0.117 [207] |∎
0.133 [204] |∎
0.149 [13] |
0.165 [26] |
Latency distribution:
10% in 0.0130 secs.
25% in 0.0160 secs.
50% in 0.0200 secs.
75% in 0.0290 secs.
90% in 0.0460 secs.
95% in 0.0900 secs.
99% in 0.1270 secs.
These benchmarks say nothing about the real world outside of our company. Because our VMware setup is different, our network is different. But for us it showed in our environment Caddy performs much better than Nginx. I guess the Nginx version waited a little too long for the file system to reject on file not found when looking for the non-existing bla.css CSS file.
The configuration had some troubles because Caddy didn't look up the folders correctly to find it's Caddyfile config. Most recent version of Caddy has no troubles anymore except our DNS challenges for our public domain - no Caddy issue.
@chilimatic Good question, I didn't look at CPU/RAM/HDD measures. Within our VMware landscape, we have different requirements than what you usually would find out there in the open.
My CentOS machines are configured using dynamic CPU/RAM. Pretty bad setting IMO but our Server-Storage-Backup team doesn't provide any other VMware to us. That's why I tried to find the fastest server for our environment.
List of servers we tested last year in September for our VMware machines:
Would be interesting to see how the current versions compete.