News for hackers. Stuff that matters.

A comment on Caddy 0.10 Released. Parent comment

Re:Caddy 0.10 Released by MichaelGG on Friday April 21, 2017 @05:21PM (#14169519)
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.

[ Parent | on HN ]
Re:Caddy 0.10 Released by StreamBright on Saturday April 22, 2017 @04:13AM (#14171617)
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=...

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.

[ Parent | on HN ]
Re:Caddy 0.10 Released by MichaelGG on Saturday April 22, 2017 @12:13PM (#14173168)
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.
[ Parent | on HN ]