4 ms·

I use it exclusively as a proxy server. I've never noticed any performance issues, I think I saw a benchmark where it said caddy can handle 2000req/s, which is

I use it exclusively as a proxy server. I've never noticed any performance issues, I think I saw a benchmark where it said caddy can handle 2000req/s, which is at least an order of magnitude or 2 faster than any upstream service I've used it in front of.

coldtea 10y ago
>I think I saw a benchmark where it said caddy can handle 2000req/s Those are application level numbers (e.g. with logic and all). Caddy should be able to handle an order of magnitude more req/s than that easily.
- anc84 10y ago
  One year ago Matt said 30000req/s: https://forum.caddyserver.com/t/can-i-use-caddy-for-a-high-traffic-site/108/15 https://forum.caddyserver.com/t/can-i-use-caddy-for-a-high-t...
- shawabawa3 10y ago
  yeah, I clearly misremembered the benchmark It was slightly slower than nginx, but not enough to impact typical applications
StreamBright 10y ago
2000 req/s is tragic. We have services with 100 000req/s so i need a reverse proxy with at least 500 000 req/s. What is the reason of this low performance?
- StreamBright 10y ago
  I am not sure why this is getting downvoted, care to explain?
  - MichaelGG 10y ago
    My guess: At 500Krps on a single proxy you're probably using 40GbE or higher right? So you're a fairly niche user and should have some sort of in-depth knowledge of this space. Your current setup should already some sort of horizontal scaling system in place. Just throwing out you "need" a 500Krps came across as fake boasting/clueless/whiny. I'm sure HN would love a more in-depth comment where you say how you're accomplishing things today and what you expect out of general purpose reverse proxies, etc.
    - StreamBright 10y ago
      If your HTTP request size is 2048 bytes and the RPS is 500000 we get 1024000000 bytes / sec that is ~ 8 Gbit/s, lets say with overhead we are hovering around 10Gbit/s. Based on the response size you can do similar calculation. As you can see in the TechEmpower benchmarks frameworks with 3M+ req/s are not uncommon. https://www.techempower.com/benchmarks/#section=data-r12&hw=ph&test=plaintext&a=2 https://www.techempower.com/benchmarks/#section=data-r12&hw=... This is on Dell R720xd dual-Xeon E5 v2 + 10 GbE. Now if I chose technology that cuts this performance 200x times I am wasting resources. I like to idea of Caddy but before we can consider using it in production I need to make sure it can keep up with the performance requirement we got.
      - MichaelGG 10y ago
        Yeah but as a proxy you need to add the request and response and you get that much full duplex. Those numbers are also with pipelining returning a tiny static response - basically as close to a TCP echo test as you can get.

coldtea 10y ago

>I think I saw a benchmark where it said caddy can handle 2000req/s Those are application level numbers (e.g. with logic and all). Caddy should be able to handle an order of magnitude more req/s than that easily.

anc84 10y ago
One year ago Matt said 30000req/s: https://forum.caddyserver.com/t/can-i-use-caddy-for-a-high-traffic-site/108/15 https://forum.caddyserver.com/t/can-i-use-caddy-for-a-high-t...
shawabawa3 10y ago
yeah, I clearly misremembered the benchmark It was slightly slower than nginx, but not enough to impact typical applications

StreamBright 10y ago

2000 req/s is tragic. We have services with 100 000req/s so i need a reverse proxy with at least 500 000 req/s. What is the reason of this low performance?

StreamBright 10y ago
I am not sure why this is getting downvoted, care to explain?
- MichaelGG 10y ago
  My guess: At 500Krps on a single proxy you're probably using 40GbE or higher right? So you're a fairly niche user and should have some sort of in-depth knowledge of this space. Your current setup should already some sort of horizontal scaling system in place. Just throwing out you "need" a 500Krps came across as fake boasting/clueless/whiny. I'm sure HN would love a more in-depth comment where you say how you're accomplishing things today and what you expect out of general purpose reverse proxies, etc.
  - StreamBright 10y ago
    If your HTTP request size is 2048 bytes and the RPS is 500000 we get 1024000000 bytes / sec that is ~ 8 Gbit/s, lets say with overhead we are hovering around 10Gbit/s. Based on the response size you can do similar calculation. As you can see in the TechEmpower benchmarks frameworks with 3M+ req/s are not uncommon. https://www.techempower.com/benchmarks/#section=data-r12&hw=ph&test=plaintext&a=2 https://www.techempower.com/benchmarks/#section=data-r12&hw=... This is on Dell R720xd dual-Xeon E5 v2 + 10 GbE. Now if I chose technology that cuts this performance 200x times I am wasting resources. I like to idea of Caddy but before we can consider using it in production I need to make sure it can keep up with the performance requirement we got.
    - MichaelGG 10y ago
      Yeah but as a proxy you need to add the request and response and you get that much full duplex. Those numbers are also with pipelining returning a tiny static response - basically as close to a TCP echo test as you can get.