Comment 1 for bug 1635416

That's correct. I don't think there's a way to tell haproxy to have "unlimited" connections, since it defaults to that value so it can set its open files limits properly on start-up. So yes, since haproxy is our default, it seems to make sense to me for this to default to 2000.

Note, in our testing, we could get to just shy of 10k connections on the default amphora image with default memory before the haproxy process on the amphora crashed. So, if we wanted, we could potentially set it a little higher than 2000. However, 2000 is probably a good place to start: Except for applications that have a LOT of long-lived connections, it's hard to even get to that 2000 limit for even high-volume sites.